We have currently overhauled the way we use jira in the company and have added the Parent feature to all of the projects, all the projects have the same parents but theyre all project by project specific.
Since rolling this out parents from ie project 1 have been used for project 2 and 3 but we want to only be able to select parent from project 1 for project 1 and so on for each project, so there is no cross linking.
Is there any way to only be able to select project 1s parents for project one and project 2's parents for project 2 etc. As when reviewing all of the issues raised in each project all of the issues are getting mixed up between each project.
Hi @louisbutler200 and welcome to the Community!
No, that is not possible. The parent field looks at the hierarchy level of your configuration and even should explicitly allow you to select issues from other projects, since - the higher up the hierarchy - the more common it becomes to put issues in a separate project.
The issues shown in the list will be restricted by a user's permissions, but if you are on a free plan, that will make no difference as permissions are not configurable there.
Hope this clarifies!
Yep, the only layer locked to a project is base-level issue to sub-task, because a sub-task is a fragment of its parent. The layer above base-level (Epic unless you've changed it) is supposed to be a way of grouping things together across projects.
You could put in a clunky botch - build an automation that checks if a newly added parent link is in the right project and removes the new data if it is not. But you're going to get people asking why their data is disappearing and why they're not allowed to use the hierarchical grouping as its supposed to be used.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Cheers both for replying!!
Is there anything else we can do / use instead of the parent feature? That can be locked to a project or made as a mandatory field
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can't think of any way to do it. Without the parent feature, you do not have a hierarchy at all.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.