John Funk Community Champion

Hello and Welcome, Girijya! We are glad you are here!!

Hi Patrick, yes, they’re probably a variety of ways to do this, including an automation rule. Create a trigger based on issue, transition, then add any conditions you might need, then add a new action for edit issue. Then, in the edit issue component, you can put in code, such as {{issue.initiator.accountID}}

Hi Jisu Lee, So sorry this happened. The only thing I can think of to do is to rebuild your issue type scheme and reattach it to the project. That may or may not work.

As Dave said, Jira will not show you text for the status of a column if there is only one status in that column. The short answer is that it will be in the status that you have mapped to that column. 

Nope - not that I am aware of. 

Hi Yongjian - Welcome to the Atlassian Community! You will not be able to add a button there. 

What type of project is it? Is the Epic issue type in the issue type scheme?

Hi Elizabeth, They are just custom fields that have set values - like pick lists/dropdowns/user picker fields, etc. You cannot use text fields or number fields. 

Hi @Varad Pingale - Thank you for the update. What if you held a 30 minute Q&A session at Team '23 so people could question and interact?

Hi Drishti, There's not a function like that natively built into Cloud. There are some third party apps that can help with it or you can build your own process. Here is an article that will help you build it yourself if you…

Hi @Shanmukha Teja Badana - Did you ever get this solved? 

Hi Marcos, What type of field is it? And how are you trying to use the field - in a email? In formula? Setting a value? 

It looks like there was a space after the {{issue. portion. That should not be there. Can you verity what it looks like now? 

Hey Phil, You can try adding a branch after the create based on most recently created issue. Then move the send email action under the branch.

There is going to be no clean way to do that without a plugin - specifically ScriptRunner Behaviours. You could try to block the transition of the issue if certain fields are not populated using a Validator and/or Condition in the workflow on the transition, but that's about it. 

I suspect it doesn't like your field name because of the slash. I would use the custom field ID instead. So that part would look like: {{issue.customfield_18563.divide where 18563 is the ID of the custom field. You can find that by going to: settings > issues > custom fields search for the custom field, the click the 3…

Now I am hungry for sure seeing all of these sandwiches! I guess my sandwich kind of depends on my mood. I general I prefer hot sandwiches like a panini or otherwise nicely melted. A lot like Summer's Hook and Ladder. But as a rule - there needs to be cheese! Cheddar, Monterey Jack, Provolone, Swiss, you name it. And then…

Hi Sercan - Welcome to the Atlassian Community! Let's take these a one at a time as you will need multiple rules. Let's deal with the issue in the TEST board moving from DONE To IN PROGRESS. Create an Automation Rule based on an Issue Transitioned Trigger - use the two statuses as you describe. Then add a Branch based on…

Hi Ayush - Sure! Can you share the details of the Edit Issue Fields step? Specifically showing the formula that you used. 

Hi Ramesh, If you are asking if there are changes to an issue in one project will it cause changes to issues in other projects just because they share a workflow - then the answer is no, there are no effects at all. 

Hi @Ivan Andrieiev First, why are you using ChatCPT? And what exactly is your question? 

Can you share two screenshots? 1. Where you ran the permission helper and it shows full access. 2. What the user sees when he tries to go to the issue. 

Hi Devi - Please create a separate question and provide the details of what you need. That way more people will see it. You can tag me on it if you like.

Hi Martine, Here is an article that will walk you through the steps of creating a board for JSM projects. It references JWM and Team-managed projects, but the process also applies to JSM. https://community.atlassian.com/t5/Agile-articles/Creating-a-Second-Agile-Board-for-Team-Managed-or-JIra-Work/ba-p/2115018

Hey Peter - please reply inline to my answer so readers can follow a common thread. Can you click on the Status that has the approvals attached so we can see what that looks like? It should look like the image below. So, click on the Status - the Include approval step. box should be check in the popup to the right. Then…

hi @IT Taupify - I assume this is all good now - can you verify? 

Hi Ayush, You will probably need multiple rules to accomplish this. Let's start with the first one. Create an automation rule based on a trigger for whatever action is taking place - for example when the Business Analyst field is updated in the Epic (so that would be a Field Value Changed trigger. Then add any Conditions…

Yes, it is. You would create an automation rule based on an Issue Transitioned trigger. Add any Conditions to make sure you narrow down which issues this should affect. Then add a Branch for Linked Issues. Choose the Link types if there is a specific one you have used for linking the two issues. Add a new action for…

Hi Sabrina - Welcome to the Atlassian Community! Have you linked the issues? 

You should have three screens, create screen, edit screen, view screen. Leave the field on the create screen and the view screen, and remove it from the edit screen.