When I try to "create a linked issue", parent field doesn't get loaded on create linked issue screen. As parent field is mandatory for the new issue I'm trying to open, Jira won't let me save it as parent is not filled out and also doens't bring the parent information (epic link) from the original issue (which is filled out properly).
How can I get parent field to be displayed on the create linked issue screen?
I see what the idea was here, and parent instead of epic link is fine, but we really miss the ability to look up by epic short name. When looking to assign to a parent it is great to be able to use a short look up like me-2024 instead of trying to remember XXX-NNNNNN.
Hi, thanks for the update. I am facing an issue, my parent field is showing the epics of all the projects in my selected project. is there any way that I can show only epics of selected project in parent field?
Does this change affect how I import sub-tasks from CSV? I am no longer able to use the Parent Id field to connect subtasks to a story in CSV? At least, I can't find a "Parent ID" field to map to in the import wizard.
There were too many comments so I wasn't sure if this question was already answered but I am so confused as to why I can't add an Initiative (custom issue) I created inside TMP as parent to Epic but I can see initiatives created in CMP.
They are not going to code for that level as I believe the plan is to one day add the ability to have hierarchy levels above the Epic level for TMP projects. I suspect it is the same for Company-managed projects that have multiple levels above Epic - I imagine the top level still has the ability to show the Parent field on it though there can't be an option for it. You should handle that with the screen by simply not putting the Parent field on the Epic screen.
The Parent field is available in Epics in Team Managed projects because those issues can be made children of Level 2 issue types that exist in Company Managed projects.
Atlassian Team members are employees working across the company in a wide variety of roles.
December 8, 2024 edited
To clarify/expand on the answers above, a TMP can only have issue types on the three standard levels (SUBTASK, BASE, LEVEL 1), while a CMP can have issue types on those levels and any user-created levels above those (provided they have Jira Premium or above).
With regards to parenting, issues in a TMP on the SUBTASK and BASE levels can only have parents within the same TMP. Issues at LEVEL 1 in a TMP, ie. Epics, can have parents in a CMP project (provided there are issues types at LEVEL 2).
191 comments