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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Been struggling with this one so I thought I'd turn to the experts to see if any of you could help.
We're using 1 project with multiple boards to filter pieces of work being run by various project teams. We've built user groups & JQL rules to ensure that each team can work from their own board without interference from other teams, but still allow them visibility of the wider programme.
We are categorising project deliverables by: "Epic Name" / "Epic Link" (if it has a epic name: "Project x", it will appear on the teams backlog & kanban board).
Is it possible to set up rules that would automatically assign a Epic Name if it is created in the backlog of a specific board?
If a user creates an issue in their backlog but forgets to apply the Epic Name, then it will disappear out of their backlog as the JQL rules are based around the Epic Name. We've asked them to remember to add the epic name but in some cases it's forgotten & if they use the "Create Issue" at the bottom of the Backlog then it will disappear
Thanks in advance for your help all!
Hi Phillip - Welcome to the Atlassian Community!
This should work using Automation For Jira, but just probably just for Classic Software Projects right now. I believe Automation has a problem with Epic assignments.
But it would be populating the Epic Link, not the Epic Name.
So the rule would look like:
Create Issue Trigger
New Action: Edit Issue
Update Epic Link field value with (probably supply the key of the Epic: ABC-123)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.