Issue appears when Creating an issue(bug) from an epic view using the "Create" button from the header navbar.
GIVEN visiting an epic
AND in the header navbar, the button "Create" is clicked
WHEN issue type is bug
AND attachments are attached to the new bug
THEN the attachments are also attached in the underlying epic
Steps to reproduce:
1. Visit an epic
2. Click "Create" from the navbar header, the create new issue module should not be prefilled with any of the data relating to the underlying epic.
3. Set issue type to bug, create description and start attaching files (copy paste of screenshots)
4. Set required fields as requested and submit the bug report.
The bug created from the "Create" navbar module should be the only issue containing the Attachments that were attached to it during task creation.
The underlying Epic, located beneath the Create issue modal (<div> element with id="create-issue-dialog") receives the same attachments as attached within the create issue modal - they are duplicated present in the new issue created, and at the same time attached to the underlying epic, that was visited and from which the navbar "Create" button was clicked
I am not entirely clear on what you are describing here (part of the problem is that you're saying "Epic under bug", which is not what the hierarchy is - Epics exist over stories and other issue types, acting as a way of grouping issues together).
I sounds to me what you are saying is this: (I find paraphrasing can clarify when I am stuck)
Is that right? If so, can you take a close look at one of the duplicated attachments in the two issues - are the urls to view/download for each attachment different or the same?
It seems that I can not reproduce this issue in a new incognito browser tab, but what was happening was:
I used a bookmark to visit an epic "domain".atlassian.net/browse/PRO-3212
From there I used the Create button in the navbar, to open a modal for task creation, and when copy pasting screenshots into the description field of this modal for task creation, the screenshots were attached also to the epic that I have navigated to from my url.
This must have been an edge case and I can not find a way to reproduce it at the moment.
Pre-receive hooks that verify the Git commit message, the modified files, and implement similar code change controls used to be requirements of large enterprises working in regulated industries only....
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events