In Jira (5.1.3), I have created a custom (Multi) checkbox
I have defined only one option (Yes), and set the default value to Yes.
When you edit a jira, the checkbox is not pre-selected, even though the default is the same as the value for that checkbox.
Is this a bug in jira? or is there something I need to do to get the checkbox pre-selected?
I have spoken with Atlassian (Jira) support, and know the answer. The configuration of the issue, whether issues already exist, and the order you do things matters.
When you set the default value, jira detects the change and tells you that you need to reindex the issues. But this does NOT set the default for existing issues though
You have to do re-index, and then select all the issues (using a filter) that should use the default, and manually do a bulk update and set their default value.
New issues after that should use the default automatically.
Related
everyone.
Is there any way of prevent some users change the Iteration Path field? I'm using TFS 2017 on premise. I'm trying to use the rule READONLY for certain TFS groups, but I'm getting an error that this is not supported for this field.
Any ideas would be really appreciated.
No. If a work item can be edited by a user, any field is eligible to be changed.
You cannot change the behavior of the area path field, as it is a system field.
I'm working with TFS 2013 and VS2013 to modify a work item template but there are some issues I cannot resolve.
I want only the person who is assigned to a work item to be able to modify this. Is there any opportunity to set a general rule for this? I already tried to set each field readonly if the authorized user is not equal to the assigned user. But that didn't work for me, I suspect this is because of the difference between display name and system user (domain).
I also want to create a custom action, which automaticly changes the "assignedTo"-User. Unfortunatly I didn't find any proper guide how to define a custom action. Most guides explanes where an action is refered in a transition, but not where it is defined. Do you have any suggestions where to find such kind of guide?
We have an existing text field 'Defect Found Version' (DFV) and a new Field I have created 'Defect Found Version Picker'
I have made the Picker mandatory & that works fine, listing all the cersions on the project.
The DFV field is set to 'Optional' on the right hand side of the Configure Field layout page, however next to the name on the left there is the text REQUIRED & I can not see how to disable this.
Even if I remove this field from all screens I get an error when I create a bug saying that DFV is required.
Any thoughts please ?
Look at the Field Configuration Scheme used by the JIRA project. Then look at the field configuration used for that issue type. That's where it is being made required. Unless it's because of the JIRA Behaviour plugin, so check if that is active
Do you have take a look on your Workflow validator ?
Sometimes, it's required on your workflow, and not on your screen.
I'm using JIRA 4.1.2. I have a page layout created using Jelly, but now that the app is in production I need to manually change a field description (can't run the script again).
The documentation says to go to Field Configurations -> Configure -> Edit, enter the text and hit update. I do that but nothing changes. HOWEVER, for a field that was created outside of Jelly, using the standard JIRA UI, an update works.
What gives? None of my jelly-created fields will update.
Thanks for any help!
Check which field configuration is being used for a specific issue.
TFS stores information about who created or who activated a work item and for some reason checks its validity whenever the work item is modified.
When a user is deleted from active directory or renamed in active directory, all work items even slightly has connection with the user can not be modified. Usually the error message is something like ...
TF20015: The field 'Activated By' contains the value 'blah blah blah' that is not in the list of supported values.
I've found a blogpost which recommends tweaking the TFS database, which is something not supported nor recommended by Microsoft.
What can be done to resolve this?
Thanks...
e-mre
Caveat: I'm not sure that this will work, and right now I'm not in a position to test it. However, I've had success with this approach on some other fields.
If you use the TFS Power Tools to edit the work item type definition, you should be able to change the Activated By field's rules and add an ALLOWEXISTINGVALUE rule to it. This might allow you to save those records when the AD name changes.
We've used this with some success with the Assigned To field.
I've seen this behaviour. It occurs if someone who activated a work item is removed from Active Directory (leaves the company) or if they change their name (gets married).
It's simple to fix, you just need to change the work item status from Active to Pending then back to Active this will change the "Activated By" field to the person chaging the status and the problem will be resolved.
Are you using TFS 2008? I seem to remember that this issue is fixed in 2010 (but I might have dreamt that)
If you have a lot of work items this blog might have a solution that helps automate the fix.