You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm working on an integration of 3 Jira projects. Each project represents a business process of our organization.
Those 3 processes are interacting very strong and relates to each other.
While our Build to order is a very detailed process about the overall engineering and shipping, the other two processes are on a more abstract level to keep our customer and a business partner informed.
We have a triplet of
and following ticket lifecycle:
During workflow transitions and updates of issue fields, data is transferred via automation between those three projects (or specifically 3 issues)
Connecting issues in Jira is done by linking issues.
Due to it's nature of Jira and linking issue, each link can edited by users.
So, while generating a ticket, those links are set, but may be changed manually afterwards.
My current solution to setup a reliable connection of tickets (as an example):
So, the reference to the customer order issue is stored at the build to order ticket and can not be changed by user.
When I need to update the customer order ticket, du to progress at the build to order issue, automation can use the value of field customerOrderKey.
This is done by using the branch rule of automation.
To be discussed:
On a DB level, all what we are talking about is a referencial integrity of a set of records by (foreign) keys.