I created an Epic, created stories related to it. Now the sprint is done. All stories have status closed and Epic has Epic status "Done" and also workflow status closed (Resolution = Done). Epic is no more visible on planning view in the board.
However, if I create a new story and want to select an Epic in field Epic link, the old Epic can still be selected. How do I get rid of the Epic in the select list of Epic link?
I have seen this:
but that did not solve my problem.
The only solution i see is to delete the Epic to stop seeing it in your autocomplete. The Epic Link field does not take see the status of the Epic, it just show all. If you want to keep your Issue you could export them in .csv and keep them in an external repository.
1-) Go to Issues.
2-) Filter the by Type: "Stories" and Creator: "yourUSER". (look for the set of testcases you are trying to remove).
3-) Click on Tools (It is on the top and right side).
4-) Select All XXX issue(s).
5-) Check the testcases that you are willing to remove from the EPIC.
6-) Click Next
7-) Cherck the "Edit Issues" radio button.
8-) Click Next
9-) Check "" and leave the Dropdown empty (DO NOT WRITE OR SELECT ANYTHING HERE)
10-) Clcik Next
Hi Felix, sorry for late response, but year end is holiday time ... I understand your approach that this will remove the Epic link from existing tickets (issue type "Story" or in my case "Task"). My problem is different: The Epic xyz and all associated stories are solved / done. However, if I create any new Story (nothing to do with epic "xyz") and want to select the appropriate epic, the epic "xyz" is still in the list of selectable epics. Over years the list will become very big, and mis-selections will happen more often. Philippe proposed to delete the epic and your proposal to remove the links from the stories to the epic would be in line with that approach. However, in that case I would lose the correct history of the development (as the epic part would be missing). Export as .csv would be a kind of workaround to limit this lost. But as I got no other approach, it is probably the only available approach currently. Thanks and regards Clemens
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG