John Funk Community Champion

Does the rule span multiple projects? 

@pnedeljkovic - you can get lots of arguments in the Community both ways as to whether it is a good idea to assign a single issue to multiple people at one time. That being said, a lot of people would disagree that there is functionality lacking in Jira to provide that functionality if it is an inherently bad idea. Not…

@Max Sudik - You are basically correct, except that Jira Software does not the have the Calendar function, nor the inline editing list function, nor the built-in form creation/display function. So there are definitely differences between the two. 

Hi Bala, You might try creating your filter and then display the results in a Dashboard gadget like the Issue Statistics gadget or the Two Dimensional gadget. 

Roadmaps are also available for Next-gen (Team Managed) Projects. But not Business projects. 

Hi Matan, Can you try to copy the Rule from the master list of rules? Got to Settings > System > Automation rules

You can try that with Swimlanes, though if you are trying to mix Sprint functions with regular Kanban functions on the same board, one of the processes will suffer. 

Hi Brad, There is a bug in Jira that won't do the update through the normal process. You need to edit the Field Configuration used by that project and update the Description there. That overrides the standard Description that comes with the field. 

Go to Settings > Issues > Custom Fields Click on the create button. You might need to add more field types as only a subset shows up. So click on the link to show more. 

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

Happy to help!

Hi Samantha - Welcome to the Atlassian Community! You will need to be a Jira Administrator to be able to add Issue Level Security. 

Hi Maya, You will need to have a Jira Premium Subscription to be able to do that. You can try that for a free trial and see if it works for you. The product is called Advanced Roadmaps. Here is some information on how to add additional levels to the hierarchy.…

You should be able to use that filter as the basis for a Queue in the project as well. If you don't have an Approvers field, you can add it as a custom field. :-)

Going to see if someone from Atlassian can reach out to you. 

Hi Shravya, To give administrator permissions, go to Settings > User Management Then search for the user. Click on the user's name Add them to the Administrators group. That will make them a Jira Administrator. 

https://jira.atlassian.com/browse/JRACLOUD-17783

You should probably go ahead and open a support ticket with Atlassian: https://support.atlassian.com/contact/#/

Hi Pete, Maybe something like: project = jira and "Approvers[User Picker (multiple users)]" = john.funk and "Approvals[Approvals]" = myPending()

Probably so as along as the two tickets are related in some way. Can you post the rule that you have? 

Great!!

Hi Andy - Welcome to the Atlassian Community! In addition to what Dave said, you can do something similar by creating a project based on an existing project. That will get a lot of the "structure" in place. Then you can use an add-on like Automation For Jira or ScriptRunner to auto-create a set of initial issues if…

I guess I would argue in this case that they are doing what needs to be done. This is a "fix" or revamping of the existing Jira Core product. The new features are anything but half-baked and are very helpful for our organization. 

Hi Daniel, You could create an Automation For Jira rule like below that should do what you want.

Hallo Eric, U kunt een voorwaarde aan de workflow toevoegen en Waardeveld kiezen voor het type voorwaarde. Het is waarschijnlijk de allerlaatste beschikbare optie. Kies vervolgens Issue Type voor het veld en! = Voor de operator en Bug voor de veldwaarde.

Hi @advyra Team - Welcome to the Atlassian Community! It is probably some type of automation that fired at that time. Maybe a Scheduled trigger automation. If you go to the Audit Log for Automation and search back to the type that the issue got updated, maybe you will be able to determine with rule fired and updated it. 

Hi Mahima, You can do something similar using Advanced Roadmaps - but that is only available for Premium Subscriptions. For regular, out-of-the-box Jira, your hierarchy is not possible. All you can do is: Epic > Story > Sub-task

Hi @csawai1 I would do it all in one project and use different Issue Types to separate the work. You could also use Components to identify the work, but with Issue Types you can use separate workflows for each type and even different screens if you are using a lot of custom fields in the project. You can still use…

Peopleの部分を手動で変更する必要があります-Automationでは変更できません-申し訳ありません。

You should be able to click on Add Column and then drag the Deploy status into that new Column.