-
Bug
-
Resolution: Fixed
-
High
-
6.3.9
-
None
-
6.03
-
Since the point of Jira agile is to manage sprints I filed this as a major since it impacts how the sprints are managed.
After upgrading to Jira Agile 6.3.9 when users without the schedule issue permission edit an issue and save it it will save it with sprint as empty. This is causing developers to accidentally drop issues from their sprint.
As as work around I added the developers to the schedule issue permission however this will not work long term as this must be tightly controlled.
If you are a customer affected by this bug, please upgrade to 6.3.9.1 as soon as possible
Follow this guide in order to diagnose and fix the broken issues: https://confluence.atlassian.com/display/GHKB/Issue+removed+from+sprint+after+editing.
Please avoid trying to downgrade the JIRA Agile installation.
If you have any further issues or need a hand with the work around please contacts us at https://support.atlassian.com
- has a regression in
-
JSWSERVER-10998 Users without schedule issue permission blow away sprint details when screen with the field "Sprint" is in used.
- Closed
- is duplicated by
-
JSWSERVER-10461 Sprint field will be deleted if a user edit the issue.
- Closed
-
JSWSERVER-10549 Issue Removed from Current Sprint After Editing Issue
- Closed
- is related to
-
JSWSERVER-10464 Sprint field displays 'None' on view issue and issue navigator when an issue is only in completed sprints
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...