Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
Description
We are the vendor of Elements Copy & Sync.
This app provides the ability to create a Jira issue from another Jira issue, and to link both issues together, as explained here: Operations - Elements Copy & Sync for Jira Server/Data Center
We are facing a problem with the “is parent of" link type. This refers to the "Parent link" field from Advanced Roadmaps, and we are experiencing technical limitations with it.
On one side, the "Parent link" field must display in the Create screen, otherwise no link is set between the source and target issues.
But, on the other side, this field is empty in the Create screen and we are unable populate it.
And yet, it works: the Parent Link is set, even though it's empty in the Create screen.
This strange behaviour is problematic because our clients are unable to set the Parent Link as mandatory. For example, if a user doesn’t use our app and use the native Jira creation screen, the "Parent Link" field should be mandatory to avoid creating orphans.
But it’s not possible to make this field mandatory as it’s empty in the Create screen when using our app, so we cannot go further.
We opened a support ticket to Atlassian and their answer was: what you’re trying to achieve can’t be done because the Parent Link field isn’t expected to prefill because it can never be a required field in Jira, and it’s a field not an issue link.
Long story short, this CR is a request for having the ability to set the Parent Link as mandatory on the Create screen.
This currently impacts many of our customers, so I hope you'll consider this.
Attachments
Issue Links
- relates to
-
WCAT-2 Loading...