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 can only find topics from 2018 about this, but recently a lot has changed at Atlassian.
How should companies use Atlassian products in 2022 to transition work between teams and different Jira software products?
1) An idea is created inside Jira Service Management.
2) Then the Product team thinks about it and writes specifications on it in Jira Work Management
3) Then the Content writers add text for it inside Jira Work Management
4) It's planned and moved to Jira Software for development
5) IT needs an extra translation and asks it via Jira to the Content writers
On top of that I use Jira Delivery management to keep track of projects...
So that's one more step and one more Jira product to maintain...
But what should we do when moving between Jira products?
- Should we just create a new card in each project and link them?
- Should we convert them to an issue in another project?
- How do we keep the information inside the Service ticket update?
Should our content writers have a license then in Jira Software as well to be able to see those tickets and add the translations to it later on?
I'm a bit stuck on:
- which licenses which type of user needs (does everyone needs to have a jira software license to support IT?)
- which Jira product should which team need to use
- create a new ticket and link OR move a ticket to a new project/software?