I added Change Status to Dropdown in my Mantis Bug Tracker. It shows only for particular users. How to Set Change status to Dropdown for all users.
You should set an access threshold by overriding $g_change_view_status_threshold in config_inc.php. By default, this is set to UPDATER. You can change this to REPORTER if you want your issue reporters to change this field. Eg:
$g_change_view_status_threshold = REPORTER;
Related
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.
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.
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.
Prior to 2.0p3 the user could choose to show hidden columns.
Is that still possible in 2.0p3? It does not appear to be, but is there an option to enable this? This functionality was nice in the previous versions, so I'm hoping it's not gone permanently.
I'm assuming you're talking about hiding and showing columns in the context of a grid.
When you are adding in your grid configuration, you must add the following config:
gridConfig: {
disableColumnMenus: false,
// more config options go here...
}
That will reenable ExtJS's default of showing the drop down menu on each grid column.
In SDK 2.0p3, we disabled the column drop down header by default due to a combination of inconsistent functionality and minor styling issues. I just filed a defect regarding this issue to make the column chooser more consistent with the rest of the app (such as the Backlog page).
I am trying to create a filter to search for all issues that were ever assigned to me, even after the assignee is changed. I cant find the appropriate search parameters for this. Is it even possible in jira?
assignee was currentUser() should do it.
It will also include issues that are currently assigned to you.
If it doesn't, try: (assignee = currentUser() OR assignee was currentUser())
I'm not sure if things have changed with JIRA since previous answers were written, but all I needed was:
assignee was currentUser()
This will pick up things that are currently or previously assigned to me.
Click the eyeglass icon on the left pane
Click on "Advanced search for issues"
On the top right, click on advanced search to open the JQL textbox
Enter the text "assignee = currentUser() OR assignee was currentUser()"
If you'll use this repeatedly, click save and name the search
Then you'll see it on the left bar under Starred...
Check out the toolkit plugin
https://studio.plugins.atlassian.com/wiki/display/JTOOL/JIRA+Toolkit+Plugin
It has a custom field 'Participant' which allows you to find all issues
that you raised, were assigned to or commented on.
Francis
2022 and still the solution works like a charm for jira version 8.20.6
assignee was currentUser()
issue in watchedIssues()
... might also be of use. It gets every issue relevant to you.
On the JIRA web application/site navigate to Issues (in header) > Search for issues, then enter your search criteria.