I have 2 issues instance and task.
For this can anyone suggest me how to approach this. It will be helpful
To enforce this restriction in Jira Cloud, you'll need to use automation rules or Forge/Connect app scripting, as Jira Cloud doesn't support direct relationship constraints natively. Use an automation rule that triggers on issue linking: if a Task is linked with more than one Instance via the "bundles" link, the rule should either remove the link or send a warning/comment. For advanced control, consider building a Forge app that restricts linking logic during issue editing. Unfortunately, Jira Cloud doesn't allow hard constraints on linking out of the box without custom development or marketplace apps like ScriptRunner or JMWE.
I don't think this is possible based on native Jira functionality, but there might be marketplace apps that provides something similar.
I have a customer with a similar use case where we have a specific work item type called Initiative that links to Epics. We have defined a specific relationship (relaizes/realized by) for the relationship between the items that we can use for searches and filters.
It is not locked or limited in any way but it is fairly easy to spot and correct errors.
You can set up your system so that many Instances can be linked to one Task — that’s fine. But to make sure a Task doesn’t get linked to more than one Instance, you’ll need to use JIRA Automation or an app like ScriptRunner.
Basically, you create a rule that checks when a Task is linked to an Instance. If the Task is already linked to another Instance, the rule can stop it or send a warning.
JIRA doesn’t have a built-in way to enforce this kind of one to many rule, so automation is the best workaround.
Hi @Kamal Deep Pareek , Could you please help me which JMWE rule will help for this requirement.
Thanks
It looks like you're new here. Sign in or register to get started.
