Hello community, I need help with an automation:
My context is the following I have 2 projects Project A(Jira Work Management) and project b(Jira Software) . In my project A I manage the master of all the projects in the area and in project B it can be a development project What happens is the following in my project A I have tasks with names of many pending, when a pending needs to be escalated to a development of software, that task is linked to project B. I need certain custom field values like the "requesting area" to be replicated from my task in project A to the user story in project B. Both projects manage the same fields.
Could someone tell me the steps to follow in the automation rules?
This is possible using Automation - can I confirm though, is the rule...
This information can help define how the rule should work :)
Ste
Sorry for my answer in Spanish
Hi @Ste Wright The rule would be:
.When you link task from Project A to the user story of Project B. The value of field "X" that already has a value configured in Project A is copied to Field "X" of the edition of project B.
The type of link would be clones. What do you mean by internal and external descriptions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The rule would look something like this in that scenario:
---
A few notes on this rule:
---
Let us know if this works for you!
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In which part do I order the Project B incident to copy the data from the Project A field. When I link From Project A to Project B. I couldn't understand what he told me
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Click on the box "Copy Source Type from Current Incident"
A pop-up will appear, and you want to choose to copy the data from the Destination Incident.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The rule causes the value to be changed in the Project A issue. The objective is to change the incidence of Project B.
Because from an incident of Project A I link to an incident of Project B.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'd give the opposite direction a try (destination issue), and see if that works - the rule would look like this:
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The rule doesn't change anything.
I have configured it like this:
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.
Hello! It's strange because before the audit came out like this and now it works correctly. In Jira does it take to update when an issue is edited?.The thing is that it already works, thank you dear @Ste Wright
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Time to complete can vary (depending on how complex the rule is), but it can be often 5-10 seconds.
Great to hear it works though!
If this answer did help you resolve your query, could you accept it? :)
Ste
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.
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.