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.
Related
I am using Django-suit for admin panel. My 'user' model has 'address' and 'contact' fields as foreign key. When trying to change the user's info, the address and contact fields has change/edit and add new options beside them. But the change/edit option remains disabled (see image).
Besides, when I click on add new icon, a new form window is supposed to pop-up. But instead it take me to the form in same browser tab. Any insight for solving this problem?
After getting question from #Efi MK, I tried once again to dig into the problem, and found my mistake with the help from this post (Django admin add related object doesn't open popup window?).
The main project was previously implemented using Django-1.6. I was extending the project by adding some new features using Django-1.11. The problem is, the static files I was using for Django-admin, were from previous version. The 'collectstatic' command didn't replace those files from previous version which has same name as new version. Unfortunately, I didn't notice that.
I deleted whole 'static' folder, ran 'collectstatic' again, and both of the problems mentioned in the question were solved. Thanks, Efi for asking :)
Is it possible to customize the "Create Issue" from per role?
In fact, I simply want to show a reduced set of fields for reporters/users to not overwhelm them and prevent incorrect filling out of unnecessary fields.
Developers should see all fields so that they can provide all necessary/internal details.
In JIRA you can install the plugin "Script Runner" which contains a module called "Behaviours". This module allows you to define fields which should be visible for a specific gruoup or not.
In JIRA we don't have ability to customise this without install plug-ins and edit templates on server-side. Maybe most easy way this is create two different screens in issue screen scheme. First screen(simply) for issue create and second screen(full view) for edit&view.
https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner/server/overview
I have a strange issue that I'm unable to resolve in Jira settings or find any information online.
Running JIRA Cloud.
The editor for the Description field is all of a sudden missing editing controls. See attached image. Screenshot is from JIRA that I edited, not from our instance. I feel like we had it couple of weeks ago and I just didn't notice it and all of a sudden it is now GONE.
Any ideas if it's a setting or add-on??
This is our editor:
In addition, the comment renderer used to render #Person links as Person Name blue link, and now it just displays it as [~Person] plain text.
Looks like the description and comment fields on your JIRA are configured with the plain text renderer instead of the wiki renderer.
If you're a jira administrator, you can go to Field Configurations, then click Configure for the Default Field Configuration (or any others you may have). Now look for the description or comment fields and check which renderer is configured for them.
More documentation available here.
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.