Hi,
I need to automate the process of creating a ticket on my Design team's board every time we create a design-related ticket in my individual project backlog. This way, they immediately see what we are requesting without the need for them to check individual project boards.
Thank you.
Hello @yaro.tarasov
Welcome to the community.
How do you know that the issue is a design-related issue? Is that identified when the original issue is created? Could an existing issue later be modified to identify that it is design-related?
Have you explored the automation feature yet? Have you tried to create such an automation rule? Are you running into a problem in your efforts?
When we create a design-related ticket, we use a "design" label and also put it into Design Epic on our board. And no, we don't modify an existing issue later to identify that it's related to design.
I have tried to find a solution using Automation future but could find the exact solution to my problem. That's why I'm trying to see if someone here can advise me on an automation rule to solve this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is your source project a Team Managed project or a Company Managed project? And what about your destination project?
Here's a starting point. Create this rule in the project where you are creating your original issues.
New Trigger: Issue Created
New Condition: Issue Fields Condition
-- check the Labels field for your label that indicates Design
New Action: Create Issue
-- select the project, issue type, and fields to set to create the new issue in the other project.
If that is not sufficient for you to work out the solution, please tell us where you are encountering problems.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's nice, thanks
But, How can I link or add in the new ticket the details of the first ticket?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Tal Stanek
This ticket is over a year old and has an Accepted Answer.
Please start a new Question to get assistance with your situation and provide the details of what you are trying to accomplish and what you have tried.
Provide screen images to show us the rule you have created.
If the information in this post is relevant to what you are trying to do, include a link to this post and tell us how you have used the information.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How can i create an automation in Jira that automatically moves to Backlog Board B when a task in a is done
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You appear to be getting help on this question in your original post
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @yaro.tarasov ,
Just to put in my 2 cents here too (especially from a multi-year agile coach & scrum master perspective as well as from jira perspective):
I´m pretty sure your requirement could be solved technically within jira automation and a Jira admin could/would immediatly start implementing.
Personally I see production/development as an holistic disciplin and (that´s really just my humble opinion) I doubt that an automation rule that "just drops" new issues in other team´s boards.
There is also possibility in Jira to have shared boards which means combining 2 or more boards within 1 board to have a common view and collaborate on topics with all the included teams and members, to get everybody on board and engaged :)
Might that be a feasable solution too?? Looking forward to your thoughts and your reply ;)
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @yaro.tarasov !
You can create an automation rule for this case.
Here an official documentation:
- Create and edit Jira automation rules
Best regards,
Alexander
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Alexander.
Can you please provide a more detailed outline of the approach I can take to solve it with automation? Not sure where to start.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.