We have a process where for a particular issue type, we need to require that it is linked to another issue. The linked issue will most likely be in another Jira project, so sub-tasks cannot be used. In the Field Scheme the field "Linked Issues" is required and is present on the screens. Yet it allows you to open a ticket without a linked issue. (My working theory is that what is actually being required is the Link Type. so "duplicate" or "relates to", and not the actual link)
You also do not seem to be able to make "Linked Issues" a "Fields Required" Validator in the workflow.
Can you require someone to provide a link to an issue? Either when creating or at some other point in the workflow?
It seems that you can't enforce (without a plugin) to have a linked issue. From Jira Suite Utilities or Jira Misc Workflow plugins you can't access the "issue links" field. But anyway, it seems to be pretty easy to write a Condition/Validator that checks this.
Perhaps using a scripting Validator ? (https://marketplace.atlassian.com/plugins/com.quisapps.jira.jss)
Take a look to this plugin:
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs