John Funk Community Champion

Hi Jonny, If you want to hide sub-tasks completely, you should modify the actual board filter and not try to do it with swimlane queries. Go to Board Settings > General > then click on Edit filter query. Add your AND type != sub-task JQL there. Be sure to save it.

Hi Philip, Let me make sure I understand. You modified the workflow that a particular project uses. But when you go the board you have been using, the new statuses that you added in the workflow are not there. Is that correct? It sounds like you might not have published the workflow after the changes. Can you verify that? 

Hi Elle, You can create additional boards against whatever projects you like. So all of those projects can have more than one board. 

Go here: https://www.atlassian.com/software/jira/service-management Then click on get it for free

Technically it is a different product, but yes the main version JSM more closely aligns with Classic Software. Then there is a second newer version of JSM for Next-gen. 

Hi Elle, There is nothing really that Core provides that Jira Classic Software projects cannot. However, Classic Software projects are capable of a little more than Core provides. Having said that, Core is different than Next-gen in that it can use share schemes and shared custom fields. JSM is more in line with Classic…

Hi @Howard, Pat - Welcome to the Atlassian Community! You could probably create a new text custom field and use Automation for Jira to populate it with a link. It would like like: yourdomain.atlassian.net/browse/{{issue.key}} You would create a Scheduled trigger Automation Rule. Then use JQL to identify the issues you want…

Hi @Shahroz Naeem , Try using Automation For Jira to calculate the difference in the fields. You would need another custom field to hold the value - also a date/timestamp type of field. Something like Incident Duration. Then to calculate the value when less than a day, use something like: {{[date1].diff([date2]).[unit]}}…

Hi @Sravani Patchipulusu - You can do that with Automation for Jira. Create a Rule with a trigger for Issue Created Then add New Actions to Create issue for each issue you want to create. 

Hola Pablo - ¡Bienvenido a la comunidad de Atlassian! ¿Puedes compartir algunas capturas de pantalla del problema antes de hacer clic en él y una después de hacer clic en él?

Hi Max - Welcome to the Atlassian Community! Why don't you just create a new custom field - maybe single pick list or Checkbox. Then place a value of Yes in the field when it gets flagged. 

Hi @AB 1 - Welcome to the Atlassian Community! The normal Kanban way to do this is to set a WIP Limit on the column. You can do that by going to Board Settings > Columns and changing the Max value for the column. That won't prevent cards from entering the column, but the entire column will light up rRed when the limit is…

Hola Andrea - ¡Bienvenido a la comunidad de Atlassian! Podría intentar crear una declaración JQL para cada grupo para un color de tarjeta. Algo como: asignee in (miguel.vasquez, ana.suarez, joel.delgado) utilizando los nombres de ese grupo. Haz un color diferente para cada grupo.

You can add a sort like that, but not by column - it will affect ALL columns on the entire board (including the backlog). And it will prevent you from manually moving cards up and down the column to adjust the priority if you have that need. So, after the most critical priority (or two) does it really matter what order the…

This is the best route to go. And it's free!

Portfolio has been replaced by Advanced Roadmaps. See if this helps: https://confluence.atlassian.com/advancedroadmapscloud/managing-releases-998651292.html

Hi Mary - Welcome to the Atlassian Community! We have a managed account and are getting ready to do a mass update of all our our emails as our domain is changing to. Here is the response from Atlassian Support to guide us: * Export a list of your managed accounts (click on Export…

Hi Maurice - take a look at this post and see if it helps you. https://community.atlassian.com/t5/Jira-Software-questions/Jira-automation-Cron-condition-every-2-weeks/qaq-p/1591412

@Sharon Curtis - it goes back to the type of workflow that it is. If it is shared across projects or it is not a Simplified Worfklow, project administrators cannot edit it. Can you share a screenshot of the workflow? 

If that works for you, can you click on the Accept answer button above to close this on out? Thanks!

You would use the queries. That's basically a filter. :-) So something like Priority = Highest (or whatever value you have)

Hi Holly - Welcome to the Atlassian Community! The easiest (and probably best) way is to create a swimlane for the highest priority.

Answers are almost always helpful! And a good way to learn. That's what brought me to the Community in the first place. 

Very extensive and great guidance!

This is always timely and helpful!

Nice addition!!

Well, that was fun - and I got all of them right! Cool little addition. Nothing stands out to me other than the ones already mentioned above. 

Can you see the issue if you run a filter for it? Project = ABC where ABC is your project. Do you see it in the list? 

Hi @randallp - Welcome to the Atlassian Community! You should add the Components field to the screen used by the project. Got to Project Settings > Screens Then edit the Create screen (or Default screen if no Create screen) to add the Components field. 

Great - glad you are up and running again with it.