Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Detail view bug leads to the wrong issue being edited - parent gets renamed instead of Sub-task


We've discovered a likely bug. The symptoms were that a number of our users were making edits (renaming the Sub-task's Summary) but finding that the parent issue was being renamed instead.

The steps are:

  1. open a filter with a list of parent issues (e.g. Stories)
  2. have the Detail view active (not List view)
  3. select a parent
  4. select a Sub-task from within the parent
  5. notice that the Sub-task's properties are shown, e.g. the Summary value of the Sub-task, not the parent, is listed
  6. edit the Summary value - expectation is that the Sub-task is being edited
  7. open both the parent and Sub-task issue individually
  8. notice that the parent has unexpectedly been updated

This happened on Chrome in both Windows and Mac. I've instructed our team to not use the Detail view or to at least not initiate edits from the Detail view. Also, it may be worse than just renaming - it may be that an attempt to delete a Sub-task may actually trigger the deletion of its parent.

The screenshot below is some evidence of the issue. Notice there is some discrepancy in the UI about which issue is highlighted. A Sub-task, 710, is selected and shown in the url. The properties (Summary) of the Sub-task are shown. But the Story (parent) issue 609 is linked twice, once as a parent and again as its own Sub-task - this is strange. 

This is the clue we used to guess that Jira was applying edits to the parent, not the Sub-task we thought was selected.

Jira detail view - subtask selected but parent story is active 2020-05-01_9-46-25.png




Log in or Sign up to comment

Atlassian Community Events