John Funk Community Champion

It sounds like you will need multiple rules to accomplish that because you can't next branches inside of each other. 

So, do all 3 have to approve before it can move? If so, you should be able to configure that when you configure your Approval. Click on the Waiting for Approval status in the workflow. Then click the Edit Approval button. 

I see that you are creating a Sub-task after the auto transition. I assume you want to assignee the issue to the Sub-task and not the trigger issue When you are creating the Sub-task, why not just add the value in the Assignee field? Click the 3 dots beside the field and click Copy. Then click on the words Current Issue…

Hi Keerthika, The logs in Jira are not very robust and will not record everything that is happening. In fact, it records very little. If you are not able to comment on an issue, are you getting an error message? If so, what does that say?

Okay, sounds like a rule with a Field Value Changed trigger. Then chose the fields that would cause the rule to fire. Next, add a Condition for Field Value, chose Issue Type field and select Equals Epic. Next, add a Branch and select Children Finally add an action for Edit Issues under the branch. Select the fields to be…

Hi James - Welcome to the Atlassian Community! Is this a Team-managed or Company-managed project? It looks like the Status got created with the wrong category (using the In Progress category instead of the Done category). If Company-managed, go to Settings > Issues > Statuses. Find the Done status and click on Edit. Then…

This is helpful stuff! I see more and more clients wanting to do this synchronization. 

You're getting soft @Nic Brough -Adaptavist- - you didn't even ask to not be shouted at. :-)

Deep Clone is a wonderful tool, but you should check with them directly to see if this is a scenario they would suggest. After you do all of the items I mention above, you will need to create Custom Fields with the same Type and Name if they don't already exist for Company-managed projects. You will also need to create all…

Hi John, Create a rule with an Issue Created trigger. Then add any Conditions needed. If this happens every time the an issue is created, but only on a certain project, then make it a single project rule and you wouldn't need any conditions - unless it only happens for certain issue types, for example. After any needed…

Hi Kevin, So what would be the triggering event that would cause the update to happen? 

Hi Andy, Make sure you clear them out of the Trash. 

Hi Sarah, If I am following you correctly, you have created a custom field for storing a user name. Then you want to run an automation that copies the value of this field into the Assignee field at some point. Correct so far? But when you are creating the automation rule, you do not see the custom field name when trying to…

Well, automation can't do that. That would be a Condition in your workflow. Just add a condition on the transition to Done for Sub-Task Blocking Condition.

Hi Archana - Welcome to the Atlassian Community! Well if it's Open, it shouldn't be marked Done. What am I missing in your question? 

Ah, then you did not follow the exact steps, because it said to start in your service project. haha. Seriously, that's the issue - seems to only be available from JSM projects. 

Great. Glad to hear.

so glad they were able to get you fixed up

Hi Harold, You can also use the Revyz Configuration Manager for Jira app in the Atlassian Marketplace that is designed specifically for that. Full transparency, I am an advisor for the app. 

Hi Ravalman, Only the far right column (last column) is considered to be done for Sprints, regardless of the status name or category. For Company-managed projects, that last column can have multiple statuses in it. 

This sound interesting - I will check it out!

I love to see the progress being made with connections to Jira and HR tools/processes. 

I love numbers like this! I don't have any interesting ones, but I have a sister and brother born on the same day 3 years apart!

It's probably a symptom of the Team-managed project and the board. You might try creating a second board using a Jira Software board connected to a filter for your Team-managed project and see if that helps. Here is an article to help guide you. If it's helpful, please give it a Like:…

Glad you found the problem and are able to continue on as desired!

Hi @Eric Zheng Not a real fan of this. And potential problems with users bypassing the process and important steps prior to the column they want to create in. If it won't let them because of a linear workflow enforcement, they will get frustrated. Is there a way to turn this off for an instance?

Yeah, not a fan of that either. It's fraught with danger for users who want to bypass the process and jump again. I would ask support if there is a way to turn this off for you instance, and if not to have them enter a ticket to add that capability. I will leave a comment as such on that announcement post. 

Hi Jemma, Yes, you can do that. Are you wanting to create an issue in the other project when an issue is created in the first project? Or do you want to link them for existing issues? 

Hi Juan - Welcome to the Atlassian Community! Create your column in the CSV with whatever name you want - Epic ID, Parent, Epic Link, etc. Put in your value of the Epic as you have: CDS-194 Be sure to have a column for Issue Type with the value of Story in your CSV. When you map the columns during the import process, use…

Hi Marcin - Welcome to the Atlassian Community! Issue Types (like pretty much all objects/configurations) in Team Managed projects are unique to that project by design. So Task issue type in Project A is not the same as Task issue type in Project B. They have different issue type IDs. So you can't do the automation using…