Hi, Some time back, we evaluated the 2.2.0 version of the Default Values plugin and it was very easy to configure. All we had to do was - Select Project, Issue type and add default values to any fields.
But with the new version, I see a new admin UI where it says Schemes and Field Configurations. How can i configure that?
Basically I am looking to do the following-
For some issue types of some projects, I would like to add default text to the Description field.
Any help is appreciated.
The procedure is quite simple:
Lets us know if that answers your question or you need further assistance.
Generally we changed the admin UI so it allows to link single configuration/template with many projects and issue types. This way you can change default value later and only once to update all linked projects and issue types. That is a great relief for JIRA instances with tens or hundreds of projects.
This feature was requested by many users but we are aware that it complicates the UI.
Thanks Gebsun, the problem has been resolved. It was due to the mis configured date format change.
But now I have a different problem. I created a configuration and a scheme. But when I try to associate with a project, some projects are missing from the Projects list. Not sure how I can see all projects in that list.
We have inspected the code and it looks like we list only projects for which current user has 'browse project' permission. We will deploy a fix tomorrow.
In the meantime you can try to adjust the settings so you have a 'browse project' permission for missing projects.
WRT the previous issue. Could you share more details what you mean by 'misconfigured date format change'? We would love to make the plugin resistant for such issues.
We have released version 3.0.4 with the fix so it is possible to configure the plugin for all projects despite of the 'browse projects' permission of current user.
BTW. This version contains also a fix for nasty bug breaking some parts of JIRA (under Java7 and some combination of project versions).
We have just released version 3.0.3 with possible fix. Please upgrade and let us know if the problem is gone.
In case it is still there, could you please take a look into JIRA server log and let us know if there is anything related?
We've performed very careful code inspection and we are almost sure that the issue happened on the server side. Therefore you should have a visible trace of the issue in JIRA log.
Many thanks for the report,
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot