Moving one ticket moves in other project

[Renato Osorio]

Hi, 

I have a very random request/questions.

We have 2 Jira boards, one is called TECH and the second is CORE. 

So I've created an automation that when something is moved within TECH board from "backlog" to "in Progress" that it will auto generate the SAME ticket within CORE. 

Now I'm having 2 issues here. One I can't tell jira to open that SPECIFIC ticket under "review", it's going into backlog and I can't find a way to change this via automations. 

The next request is a weird one, I'd like for a way that these 2 tickets can move simultaneously when being moved between their respective Jira Boards. Is there a way?

I know I may be asking alot here, but just because when it is in TECH board under in progress it will then be reviewed if we implement or not, but would be great for it to stay up to date on the other ticket, other than being linked. 

Thanks, 
Renato

[Jack Brickey]

When issue was created it will start off in the initial status as defined by your workflow. If you want issue to be in a different status then you must transition it post create. So you could use automation to trigger on issue created and based on certain conditions transition issue to the desired status.  regarding your second issue I’m really not following to be honest what do you mean by having the two tickets move simultaneously?

[Renato Osorio]

Hi Jack, 

regarding the first part. I have set the below rules, but it is not triggering the move. I have checked and we ONLY have this one rule where Automation for Jira is being used as the reporter. Any ideas of what else I could use?

The second issue, which may be a separate "ask community", basically, once all the moving part are set, lets say I have ticket TECH-1 and CORE-2, which are both linked, one is under the status of "in progress" and the one in CORE is under "Selected for Development". When it's being moved between status either in TECH or CORE, i'd like for it to move along the same status (both of the Jira boards have the same status except for Selected for Development and in progress). 

Sorry if this doesn't make sense, I can send some screenshots of what I mean. 

Thanks,
Renato

[Jack Brickey]

For the first question ensure that the rule, that is the rule you show above can be triggered by another automation rule. There is a tick box when defining the rule.

For the second question, yes you can certainly have a linked issue follow the status of the other issue. I haven’t set this up myself but it should be pretty straightforward I think. The trigger is an issue transitions then define your conditions to include link field and set the status of the link to that of the issue that triggered the event. You might search the community for this as well. I seem to recall similar questions.