John Funk Community Champion

Great! Glad you got it working. 

Great! Glad that worked for you. 

Sorry for the delay. Yes, I use it a lot. And in fact, I am also an Advisor to the app. :-) How did it go? 

You should ask them. :-)

Yep, hopefully they will get that added soon. Were you able to attach that field type from the global fields and use it in the Team-managed project? 

That's strange. I am wondering if it is a caching issue with the browser. You might try clearing your cache or try another browser. Or try with Incognito mode.

Hi Fabio - Welcome to the Atlassian Community! It is probably in the screen Workflow Screen - 14 that is attached to the transition. Either remove that screen from the transition, or modify the screen to remove the Resolution field, or use a different screen. 

Hallo Sascha – Willkommen in der Atlassian-Community! Du kannst den Benutzer als Gast hinzufügen und ihm Zugriff auf einen Space gewähren.

Sure, you can do two fields. But you will need to create a custom field for each form field that you want to use. Then in your automation rule to Edit Issue for the Summary, it will look like this: {{issue.Field 1}} {{issue.Field 2}} - {issue.summary}} So if Field 1 values is Green and Field 2 values is Acres and the…

Hi Neeta, You can do this out of the box. You can create an Automation rule to create the Epic in the desired Jira Software project. This can be either manual trigger that an Agent executes, or it can be an automation trigger that will fire on the JSM issue being created based on certain Conditions. 

Hi Soukaina, Are there Conditions on the transition from In Business Requirement to In Blueprinting? If so, what do those look like? 

Hi @Tharunkumar B When you migrate/move issues like that from one project to another, you need to take a few things in mind. If issues in Project A use Components, Releases, and/or Custom fields that have a Context just for Project A (or at least do not include Project B or are not Global), those items need to be setup in…

Hi Red, I would create a project per Customer. Then create Epics for each "project" for that customer. And you can certainly setup automation rules to create new Epics and associated pre-defined tasks/stories for the Epic using automation rules. And that's all built into Jira Cloud - you don't need a plugin. 

You are welcome. Just realize that your existing issues will not be automatically updated. If you want to use any of the not completed issues, you will need to manually update the field in those issues. Also, if this solved your problem, would you kindly click the Accept answer button above so we can close this one out?…

Hey @Marc -Devoteam- - The question states that the status is in the last column of the board. 

Hi Roopesh - Welcome to the Atlassian Community! Is there some type in the status of the issue in the History of the issue? And does it happen to all issues in the Sprint? Or just a few? And do the issues have any sub-tasks?

Technical issues and bugs

Hi Nikhil - Welcome to the Atlassian Community! You need to hope a support ticket with Atlassian to have them check the suppression list for the email address. https://support.atlassian.com/contact/#/

Hi Louis - Welcome to the Atlassian Community! Your best bet in the short term is to create a custom field. Then in your form, link the custom field to the form field. Then refresh your automation rule. You should be able to use the new custom field in your rule then. 

Hi Rishi, What type of project are you importing into? Team-managed? Company-managed? Are you creating the parent at the same time you are importing the children? Or just creating children and attaching to an existing parent?

Great! Glad to see this rolling out. 

Hi Krishna, Can you share a screenshot of the workflow that you have? And please include detail screenshots of the approval steps. 

Awesome - best of luck!

Hi Shabista - Welcome to the Atlassian Community! What I have done in the past is to create a custom number field. Then create a scheduled trigger that runs once a day. Use a JQL that selects the issues that you want the rule to run against. Then add an action for Edit Issue. There select the custom number field. Then in…

Hi Sreedevi, Can you share the entire rule here? Along with screenshots of the relevant detail steps? 

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

Hello Emmanuel! We are glad you are here!

So bottom line is that a Sprint completed action will trigger an automation rule, but a Sprint started action will not. Is that correct? If so, wondering if you could do some type of workaround where you set the value of a custom field when the Sprint is completed. Then when you Start a Sprint, you somehow read the value…

if you type the full email address you should be able to click on it when you are finished typing it. 

Hi Dan - Welcome to the Atlassian Community! Jira Cloud is not formerly Next-gen. Jira Cloud was around for a long time before next-gen projects arrived. Those have been rebranded to Team-managed projects. Company-managed projects are still the flagship project type for Jira Cloud. Now with that out of the way, it does not…