Jira Softwareにおいて、異なるProjectにあるEpicの内容を自動化で同期させたい

[北林洋悦]

DataCenter版jira Softwareにおいて、Project AにEpic A1を作成し、これをCloneしてEpic B1とし、Project BにMoveします。

業務において、Epic B1のStory Pointsが更新された場合に、Epic A1のStory Pointsも同じ値になるように自動化を考えていますが、Epic B1にリンクされている Epic A1を特定する方法がわかりません。

クラウド版の場合、JQLを使って”課題を検索”するメソッドがあり、
issue in linkedIssues({{triggerIssue.key}},"clones")
のようにできるのかもしれませんが、DataCenter版には”課題を検索”するメソッドが無いため、どういう方法で特定すれば良いかご教示ください。

[Ste Wright · Accepted solution]

Hi @北林洋悦 

You should be able to do this using Branching. I did only test this in Cloud, but I believe all the parameters exist in Data Center.

You'll need to:

• Create this rule as a multi-project / global rule, as it spans 2+ Projects
• Ensure the 2 Epics are linked
• Perhaps use a unique link type, or set additional Conditions, so other issues using that link type aren't updated unnecessarily 

---

• Trigger: Field Value Changed
  • Field = Story Points
  • Change = Any change
• Condition: Issue Fields Condition
  • Field = Issue Type
  • Condition = equals
  • Value = Epic
• Branch: Related Issues
  • Type = Linked Issues
  • Link Types = blocks, is blocked by - examples only
    • Branch-Condition: Issue Fields Condition
      • Field = Issue Type
      • Condition = equals
      • Value = Epic
    • Branch-Action: Edit Issue
      • Field = Story Points
        • Action = COPY FROM - choose from breadcrumbs menu
          • Issue to copy from = Trigger Issue
          • Field to copy from = Story Points

---

Let us know if this works for you!

Note: I did try to re-translate this back into Japanese but it made less sense, so hopefully this still helps!!

Ste

[北林洋悦]

Thank you VERY much.

Data Center版でも正常に動作しました。

とても助かりました。