-
Suggestion
-
Resolution: Unresolved
-
None
-
5
-
1
-
Problem Definition
Currently, if the Parent link field is exposed to issues in issue page, user can add any issue including those outside Portfolio plan to use the parent link.
User would like to limit the option available to the options available in the Parent link field so the options will only be available to the issues which are available in the same Portfolio plan as the parent issue.
Suggested Solution
- Option 1: Limit the option available to the options available in the Parent link field so the options will only be available to the issues which are available in the same Portfolio plan as the parent issue.
- Option 2: Limit issues available in the Parent Link field based on the JQL query.
Workaround
None. To prevent users from adding undesired issues to the parent issue, remove "Parent link" from issue page and link issues to the Parent issue from Portfolio plan.
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-24833] Limit *Parent link* option to specific project
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC
Our Parent Link field options are growing exponentially and the list is rife with resolved choices. Please support a solution for this that allows at least some limited filter settings for the selection. This is already done with a different plugin called issuepicker. Please mimic their design.
When creating or editing an Epic issue, the Parent Link field will show every issue in the lowest Jira Portfolio hierarchy level (i.e. the level immediately higher than Epic). This is a major pain, because there can be a lot of possible issues to choose from for Parent Link. Even when issues of this type get closed, they still appear as viable choices for a Parent Link.
The change requested here is to populate the Parent Link field based on which Portfolio Plan(s) the current project is a source to. But another way to go about this is to provide a project configuration option whereby an arbitrary JQL filter could be specified to populate the Parent Link field for issues in that project. This would allow fine-grained control over which items appear as choices in the Parent Link field. For example, users could configure this filter for a particular project to include only issues at the lowest Portfolio hierarchy level which (1) have a status of Open, and (2) are associated with a specific issue at the next higher hierarchy level.
**If JPOSERVER-2350 is ever implemented, then there will be even more choices for Parent Link (this feature suggestion would allow issues at any level within the Jira Portfolio hierarchy to be selected as a Parent Link). So limiting the Parent Link choices based on an optional JQL filter may be a better long-term approach.
This is a constant issue for our teams. We handle multiple projects and would love to make this a better user experience.
We never have a need to associate an issue being created in one project to a different project