Fazila Ashraf Community Champion

@Ashot , You could look at the documentation in https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-get 

Hi @Amanda Schofield Am curious about your use case. So when an issue is assigned to a user, you would want to reassign it? And wont it keep triggering the automation again?

@Manaswi Shimpi , so sorry! I just saw your comment. I hope you got the solution that this instruction is for on-premise installs and not cloud much early!

@Anson Osbourne , by 'no changes were applied', do you mean that it still reflects the old server id in the page? was a restart done? Please share more details.

@Abhishek , it helps if your board has 'tracking remaining estimate' option set.. Also, to reflect the reality that when the task is set to done, there is no remaining effort - this automation helps.

Ah ok.. Got the use case :) Setting the flag actually sets the value 'Impediment' to the field 'Flagged'. In you groovy code, you can update the ticket's flagged value to Impediment to achieve this. Refer to an existing…

Hello @Pawel By Flag, what do you envision? How are you going to consume that flag? If it only to query all the overdue issues, cant we query it with JQL itself? Basically am trying to understand the usecase to give you an appropriate solution :) 

We will need the exact steps that you followed to see whether there can be anything different that you should have done.. Could you share that?

Hi @fnusla Could you let us know the steps you are following to upgrade?

Hi @Ayush Mishra So when the subtasks of the story is not completed, then the story is not actually completed and delivered right.. So why would you export only subtasks to next sprints with out the story?

Hi @Gargi Panchal There is also a transition 'all statuses' to Done. Can you update the post function there as well?

If you are using server/datacenter deployment and have scriptrunner, you could write some behaviour scripts to achieve this. But with my experience, i do not recommend this. For JIRA to be used as a standard agile project management tool, ask the end users to use it how it is designed to be used, following agile…

@[deleted] That is correct. 

Hi @Reed Jarvis Welcome to community! * Could you check whether your email client has some rules moving the notifications to other folders/junk? * Any email organizational policy blocking you to receive these emails? * Tested with other users in your team? Atlassian community can help you with pointers to investigate but…

Hi @[deleted] To achieve the goal, you should simply not have 'Sprint' field on the issue screen. There are lots of side effects that you would face even if you find a workaround to restrict the sprint choice to Backlog (there is no option to restrict as far as i know). You should simply use the agile board's built in…

Hi @D_ Stokes Could you recheck whether the correct screen is mapped to the create issue operation for issue type TEST in project eScribe Xray? The screen configuration (even for general) do not match the view you show on the create operation.

Hi @Marcos Ferreira If the common board's filter scope is wide enough to cover both the sprints' issues and both teams has browse access to the issues in both sprints, then there is not way to restrict. You could look at having 2 different scrum both for the teams and adjust the scope of the issues through the board's…

Works both ways..You could subscribe the filter to a group. Individuals also can subscribe to it.. Results will be like how that particular individual will see in the issue navigator. If they don't have access to certain issues, they won't be in their results

Ah ok.. but note that it is not feasible in JIRA 🙂

Happy to help! You could choose to accept the answer, so users with similar questions will get to this answer faster 🙂

Hi @Joseph Dennis Welcome to community! Why automation for this use case? Have you look at the 'Subscribe to search results' in https://support.atlassian.com/jira-software-cloud/docs/work-with-search-results/ ? Is there something additional that you want to achieve?

Hi @PRAMOD KUMAR REDDY KASIREDDY If you do the changes in different JIRA instances like PROD and UAT and then want to move changes from UAT to PROD, then you could look at plugins like https://marketplace.atlassian.com/apps/1211147/project-configurator-for-jira?tab=overview&hosting=server I think they could be performing…

Hello @anita.tempert There are commercial plugins that could help with the feature that you are looking for.. Plugins like https://marketplace.atlassian.com/apps/1218390/calendar-for-jira?tab=overview&hosting=server Not exactly the same but if your requirement would be satisfied if the tasks are placed in a calendar view…

Hi @Badana Shanmukha Teja It is not possible to do so. You can identify the subtask from the issue type name. Is there a reason why you would want the . values?

@Karuppu , you can ask the creator of the filter to add you or the administrator group as "Editors".. Or.. you can change the ownership of the filter to you and do the same..

Hi @Durga For this use case, you can put automation to create subtasks 1,2,3 while the parent task enters status A. And when the status changes from A to B or C (transitions), you can set to close the tickets or set view restrictions via issue security - what ever your process wants.. While we can technically do what i…

Hi @Ashish Bijlwan Yes, you can :) 

Hi @James Chen Keep the status name as "Awaiting estimation from engineer" or something that is meaningful and then create a new transition "Estimate completion date" to status "Estimated" (or again something meaningful) that is visible only to the responsible group and have the 'estimated completion date' in that screen…

Haven't done that in cloud but a quick search got me this free plugin that could help with this use case https://marketplace.atlassian.com/apps/1224410/manage-users-for-jira-cloud?tab=overview&hosting=cloud Hope it helps... Let me know

@[deleted] , I have used the above highlighted plugin for this same use case..