John Funk Community Champion

Hi @Bartosz Kanak A couple of questions first - what type of project is it? Next-gen? Classic Software? Business? Also, what have you done to try to add the issue to the release? Have you tried to Edit the Fix version field on the issue to add the Release? 

Hi Ankit, Deactivating a user for Jira only deactivates that "product". But the user is actually set up at a level above the products level - the Atlassian level more or less. So you will need to Deactivate the account itself. If it is a Managed Account, click on the Directory link in the top navigation bar. Then search…

Hi David, Make sure the Reject Status is in the last column. Only statuses in the last column on a Sprint board will be considered "Done" and not moved. 

¡Gracias, Vero! ¡Y les deseo un Feliz Año Nuevo también!

Has anyone submitted a Support Request with Atlassian? https://support.atlassian.com/contact/#/

Yes, go to Settings > Issues > Screens and search for the appropriate screen. Make a copy of the Default Screen and label it as the View screen. This screen should have the non-edit field in it. Then go to Settings > Issues > Screen Schemes and search for the appropriate Scheme. Click on Configure under the Actions heading…

There's probably a couple of ways to do that. One is to set the value of a custom field when the status moves to Reopened. Then check the value of that field in a Validator when moving to the status in question. Another is create a new Transition from Reopened to InProgress to force the user to navigate to that Status.…

See @Ravi Sagar _Sparxsys_ video below. 

Hi @Dmitriy Bokhanov You will not be able to put the field in the default Edit screen and not make it editable. You have to remove the field from the Edit screen, but leave it in the View screen. Then add the field to a transition screen. Then add the transition screen to a new looping transition on the status where you…

Go to Board Settings > Card Colors

Hi @[deleted] - when you say that you want a rule for when user makes any update, can you be more specific? I am not aware of anyway that Automation for Jira can read if any update happens but only for specific fields. 

Hi Samuel, You should be able to include in your query this: status was in reopened

Hi Liza - Welcome to the Atlassian Community! Filters for the boards determine what issues show on the board. So you just need to update the filter for one of the boards to include the issues you want to see. What we do for each project is to have a "Master" board that includes ALL issues on the project. Then we create…

Feliz Navidad!!

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

I have this same problem sometimes with a handful of users. I don't know what makes them different, I just know to try the email address or username if the name doesn't show up when I start typing, and I know they are valid users. 

Hi @cia - You must be a Project Administrator to do a release, not just a Board Administrator. 

Hi @Pascal Laub - You would need to use the ASC instead of DESC to get the nulls at the bottom, which, unfortunately, will change the order of the issues that actually have a Due Date. Your other option is to use a filter that specifically ignores issues with no due dates (duedate is not empty). You could create another…

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

Hello and Welcome, Nikita! we are glad you are here!!

Hi Omer - Welcome to the Atlassian Community! Simply create the filter(s) that you want using the Reporter in the filter. Then use a gadget such as the Issue Statistics gadget or the Filter Results gadget to place in your dashboard.

Sorry, I posted that response in the wrong post. :-( Let me take another look here. 

Hi Sheyman - Welcome to the Atlassian Community! Roadmaps do not appear to be available for Jira Core (Business type) projects. You will need a Classic Software or Next-gen project to be able to do a Roadmap.

Maybe try creating an additional transition to Done for Sub-tasks and add a Condition to the transition for Issue Type = Sub-task. And then place the Deep Clone post function there. Then update the existing transition to Done to add a condition for Issue Type != Sub-task. 

That will be a fantastic addition!

Hi Mathew, Yep, you can do that. Just follow this handy guidance: https://support.atlassian.com/jira-software-cloud/docs/migrate-between-next-gen-and-classic-projects/

Great! I am glad I could help a little. 

Hi Kryzysztof, Can you share the Automation rule that you have created so far? And also what it is not doing that you would like for it to do?

There are no associated items that it ran against - which was what I suspected. Can you share the query you used under the When: Scheduled 7 days details? 

Can you share the audit log of the rule that you ran? It appears that no issue match whatever condition you might have in the rule.