An Epic had 14,000 tickets linked to it. When I did something, the Epic Link was removed from all the tickets. I have no idea what I did to change the settings.
What operation caused Epic to be removed from all tickets?
Any advice?
Hi @視恵 手塚 , welcome to the community.
It is worth noting that "epic link" has been deprecated and replaced by "parent ". Is it possible that the parent field still exist for these 14,000 issues? If your parent field is empty, I'm afraid there's no way to query for "parent was…".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
if something has resulted in you clearing the parent field on any number of issues then unless you have some means of identifying them via a JQL query, such as label or custom field value, etc. then there is no way to easily recover the parent information.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If there were as many issues affected as you said then it was likely a bulk edit action.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello every one ,
I am just reading the question trying to be more familiar with Jira .
About the issue we have on top by @視恵 手塚 it means that there is no automatic way to relink a specific issues by label or date with the parent Epic ?
Assuming that I have a lot of issues I have to pass one by one or there is an automatic way ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can use bulk edit if you can identify the issue to be edited using JQL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @視恵 手塚
Welcome to community!
Sorry to here about this event :(
Was there any change to the global issue hierarchy configurations?
Or was this particular Epic was converted into a different type and back?
Or it could be possibly done by an automation?
Did the parent field value also reflected the change?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Fazila Ashraf Thank you for your reply.
Was there any change to the global issue hierarchy configurations?
→Probably not.
Or was this particular Epic was converted into a different type and back?
→No, the set "Parent" has been removed. In the ticket "ALL" under "Activity", the following history remains
<My Name>changed the ParentMay 15, 2024 at 5:02 PM HISTORY
<Parent Name>→None
<My Name> updated the Epic LinkMay 15, 2024 at 5:02 PM HISTORY
<Parent Name>→None
Or it could be possibly done by an automation?
→No.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hmm.. what else do you see in the history before the parent became none?
Also what do you see in the child issue's history?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am sorry, but I do not understand 'parent' and 'child' very well.
Perhaps the 'child' has not been created.
The situation is that all the tickets have the same 'parent', but the parent has been removed from all the tickets.
In other words, the tickets have a history of me deleting them (as explained), but I have no idea what I did.
However, the tickets have already been reverted to their original 'parent' status.
I would like to know what action caused this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Spend the day sharpening your skills in Atlassian Cloud Organization Admin or Jira Administration, then take the exam onsite. Already ready? Take one - or more - of 12 different certification exams while you’re in Anaheim at Team' 25.
Learn more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.