-
Bug
-
Resolution: Fixed
-
High (View bug fix roadmap)
-
6.2
-
6.02
-
Problem
Both in project specific configuration and global configuration.
A project that had a field which was then removed was not able to be configured again.
To reproduce:
- Create a sample scrum project
- Go to classic mode
- Click Tools > Configuration
- Look at Rank field - no way to add a new one
In test data, e.g. QuickFilters project, there is a field listed. It can be removed, then you get to the same state where you can't add another one.
Cause
As of JIRA 6.0, the class CalculatedCFType, from which our RankCFType class extends, is no longer a SortableCustomField. This causes Classic configuration to not recognise the rank field as a valid option.
Work-around
The Rank field is still able to be used for projects which use the Scrum Project Template. If you can alter your project's configuration to use this template instead, then you should be able to use the Rank field.
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- caused by
-
JDEV-14917 Failed to load
- mentioned in
-
Page
No Confluence page found with the given URL.
-
Page Loading...
-
-
-
-
-
-
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-8933] Classic - cannot configure Rank field for project
You will have to raise a support request to get the build installed on your OnDemand environment. But actually I don't know if they will allow it, as it is a non-standard build.
Rest assured, we will roll out the proper fix as soon as possible.
EPT
added a comment - I've got the snapshot, Thank you!
Is there a way we can upload this build to a On-demand environment? please let me know, Thanks!
EPT
added a comment - I've got the snapshot, Thank you!
Is there a way we can upload this build to a On-demand environment? please let me know, Thanks! OK, Thanks a lot! please sent the snapshot and I'll install on my server, Perhaps my retested email (wangyn-a@glodon.com) have a attachment upload limit, so please send it to both (wangyn-a@glodon.com and walterwyn@gmail.com)
Or can you upload the snapshot build to this BUG issue, so everyone can download it and fix this issue?
Is there a way I can upload this build to a On-demand environment (https://lezyou.atlassian.net)? because this team faces the same problem. please let me know how to do this. thanks!
EPT
added a comment - - edited OK, Thanks a lot! please sent the snapshot and I'll install on my server, Perhaps my retested email (wangyn-a@glodon.com) have a attachment upload limit, so please send it to both (wangyn-a@glodon.com and walterwyn@gmail.com)
Or can you upload the snapshot build to this BUG issue, so everyone can download it and fix this issue?
Is there a way I can upload this build to a On-demand environment ( https://lezyou.atlassian.net)? because this team faces the same problem. please let me know how to do this. thanks!
wangyn-a the snapshot build of the plugin which contains the fix is too large to attach here.
I will send you an email to the address registered on your profile.
My project's Issue type and workflow is not compatible with Scrum Project Template, A "Chaning Template-Scrum" popup window says:
"The currently selected issue type scheme for this project is not compatible with the Agile Scrum Issue Type Scheme.
Please migrate to the Agile Scrum Issue Type Scheme by associating your project via Issue Types in the JIRA Administration console. Contact a JIRA Administrator to perform this migration."
We really need a better work-around, better a new build of Agile plugin with this issue fixed Thanks very very much!
EPT
added a comment - - edited My project's Issue type and workflow is not compatible with Scrum Project Template, A "Chaning Template-Scrum" popup window says:
"The currently selected issue type scheme for this project is not compatible with the Agile Scrum Issue Type Scheme.
Please migrate to the Agile Scrum Issue Type Scheme by associating your project via Issue Types in the JIRA Administration console. Contact a JIRA Administrator to perform this migration."
We really need a better work-around, better a new build of Agile plugin with this issue fixed Thanks very very much! I have found the root cause of this issue. It is caused by a change in JIRA's API from 6.0 onwards. Ranking configuration in Classic boards works as expected on JIRA 5.2.11 and below.
We can fix the issue on our side as well - we just need to update the code to comply with the changes to JIRA's API.
I will update the description of this issue with a work-around.
Yeah, Thanks very much! Michael !