-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
6.6.41, 6.6.51, 6.6.70
-
None
-
6.06
-
Steps to reproduce:
- On JIRA Agile, copy a board
- Notice that the Administrators field is empty and it has not been copied to the new board.
Expected behavior:
All fields of the board should have been copied including the Administrators field.
Workarround:
A JIRA administrator can configure the board and add the desired admins for the board.
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[JSWSERVER-11604] Copy board does not copy administrator
pablo.gonzalez, the best place to view updates for JIRA Agile is the release notes via https://confluence.atlassian.com/display/AGILE/JIRA+Agile+Release+Notes
JIRA Server customers can view upgrade notes via https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.7+Upgrade+Notes
Kind regards,
Martin
JIRA Agile
Pablo Gonzalez
added a comment - Hi Martin, we have a Jira instance installed in our own servers with the latest version of 6.4 as shown in this page: https://www.atlassian.com/software/jira/whats-new
How is that the 6.7.0 is not promoted in that page yet? And, how can we upgrade to the 6.7.0 if it's stable?
Thanks for your feedback.
Pablo Gonzalez
added a comment - Hi Martin, we have a Jira instance installed in our own servers with the latest version of 6.4 as shown in this page: https://www.atlassian.com/software/jira/whats-new
How is that the 6.7.0 is not promoted in that page yet? And, how can we upgrade to the 6.7.0 if it's stable?
Thanks for your feedback. 
Nicolas Bier
added a comment - I'm confused. Is this bug fixed in 6.7?
It's in the 6.7 release notes.
Nicolas Bier
added a comment - I'm confused. Is this bug fixed in 6.7?
It's in the 6.7 release notes. Hi craig.emery,
We do not backport fixes to earlier releases, so the only way to get this fix is to upgrade to the versions I mentioned previously. If you need any help with the upgrade please do contact us at https://support.atlassian.com and we will be glad to help out 
Regards,
Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].
Craig Emery
added a comment - Hi @florian
I think @oswaldo is actually asking for the fix to also be implemented in / back-ported to the version of Jira Agile that does run on Jira 6.2 - whichever that version happens to be.
I hope you know what version that is.
Craig Emery
added a comment - Hi @florian
I think @oswaldo is actually asking for the fix to also be implemented in / back-ported to the version of Jira Agile that does run on Jira 6.2 - whichever that version happens to be.
I hope you know what version that is. Hi florian.zink,
Unfortunately the earliest compatible version for JIRA Agile 6.7.0 is JIRA 6.3.x, so you will need to upgrade JIRA to at least that version in order to install 6.7.0 and get rid of this bug.
Hope the information helps.
Regards,
Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].
Florian Zink
added a comment - Hi @ohernandez ,
will you be offering a 6.7.0 agile version for JIRA version prior to 6.3? I'm running JIRA 6.2 but would also like to get rid of this agile bug.
Florian Zink
added a comment - Hi @ohernandez ,
will you be offering a 6.7.0 agile version for JIRA version prior to 6.3? I'm running JIRA 6.2 but would also like to get rid of this agile bug. Hi edgar.garcia,
I have updated this already. Thanks for pointing it out, a fix for this is currently under review and should be available in a JIRA agile release soon. We'll update the issue as this progresses along.
Regards,
Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].
Its not enough.
Our case:
In the above conditions jira-administrators just can't see that board at all.