I have a scenario whereby an initiative has been linked to another initiative. I want to remove the parent link so that they are stand alone initiatives.
Does anyone know if there is away to do this?
Background:
We have a structure of Initiative >Epic > Story and are using Portfolio so have the Parent Link field enabled.
Therefore when we assign a link we are using the Parent Link field to associate all the epics under an initiative and use the Epic Link to associate the stories to the epic.
What someone has managed to do is use the Parent Link to associate and Initiative to an Initiative and we are now unable to remove this link. They should not be associated with each other as they are standalone.
Hi Joanne,
A couple of options here.
Add Parent Link to Initiative screen:
Use Bulk Change (better if you have more than one to fix):
By the way, this happens when someone clones a child of an Initiative (in your case an Epic that has a parent Init), or creates a new one and sets the Parent Link, and then, through one means or another, converts that Epic to an Initiative. Even though a Parent Link on Initiative is "illegal" Jira still retains the value in the Parent Link field.
This is difficult to fully prevent. You can remove issue type from the edit screens but there are two other ways in which a user can change the type of an issue. Bulk Change and when Moving the issue from one project to another. Pretty frustrating!
If you haven't already you'll notice this causing problems with certain issue searches. If you have an issue search, for example, that looks for EMPTY parent links, the issues with "ghost" links will NOT be returned. Moreover, you would expect that if you did a search for these issues and added Parent Link to the columns that you would see the value in Parent Link, but you don't. So on the one hand Jira is showing you the field is empty, but on the other hand it's treating it as a non-Empty field!
There is a suggestion regarding this problem... maybe you can go and vote for it! Thanks!
If "Initiative" is at the top of your hierarchy, then the solutions you presented unfortunately do not work.
In the Issue View screen, the field is not click-editable, but shows a warning triangle.
In the Issue Edit and Bulk Edit screens, you see the following:
and it's similarly not editable.
The only solution is to bulk change the affected Initiative(s) back to a lower type (e.g. Epic), remove the parent link, then convert them back.
However, if they now already have Epics linked to them, I'm not sure what would happen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have discovered a quicker fix:
In Manage Apps > Advanced Roadmaps > Hierarchy configuration, add a new entry above "Initiative" and save. You do not even need to select an issue type.
In the affected Initiatives, you should now be able to edit (and blank) the Parent Link field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not sure what you need. In JIRA only subtasks have parents. You can convert a subtask to a standard task if you have permission to do that.
when you say 'linked to another' that implies two issues linked together. You can delete the link. See https://confluence.atlassian.com/jirasoftwarecloud/linking-issues-776997756.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have a structure of Initiative >Epic > Story and are using Portfolio so have the Parent Link field enabled.
Therefore when we assign a link we are using the Parent Link field to associate all the epics under an initiative and use the Epic Link to associate the stories to the epic.
What someone has managed to do is use the Parent Link to associate and Initiative to an Initiative and we are now unable to remove this link. They should not be associated with each other as they are standalone.
Hope this makes sense
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not familiar with the Portfolio plugin so I can't help. In the future I suggest if you're using a plugin to perform a function mention that in the title or description. You're more likely to get better responses.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.