John Funk Community Champion

Hi Steve, The quick answer, unfortunately, is you can't. Hopefully, that feature will come soon, but for Next-gen projects it is not available. You would be able to add Quick Filters to a Classic Software project. 

Hi Wei, You should create that as an Automation For Jira rule and not do it in the post function in this case. So create an Issue Transitioned trigger rule. Then add any conditions you might want. Then add a New Action for Edit Issue. Select the Rework Count field and add your above code into that field. 

Hi @Capillary AccessControl - Welcome to the Atlassian Community! Access is granted to projects (and their issues) by way of the Permission Scheme attached to each project. And then specifically, the Browse Project permission inside the scheme. So you can create an external user as normal, but then put them in a project…

Hey @PhilSpo - try this one: {{issue.Target start.toDate.shortDate.format("dd/mm/yy")}}

Hi Gloria, Do a double check on the context for each field to be sure they are available for both the IM project and the Managed Change issue type. Go to Settings > Issues > Custom Fields Search for the field Click the 3 dot menu on the right hand side and select Contexts and default values Modify as needed. 

Hi Sandro - Welcome to the Atlassian Community! It is always best to copy the current default workflow and make changes to the copy before deploying. There you can add new statuses, modify transitions, add conditions and validators and post functions, etc. I would also create a new Workflow Scheme and attach the new…

Hi Jane, The Summary field is always required on every issue type and there is no way to change that. Make sure the field is on the Create Screen. I see that it is in your last screenshot but I am suspicious that this is not the system Summary field as it does not have a red asterisk next to it. The other think is to check…

Hi Michael, I believe that functionality for linking to Next-gen Epics is currently not functioning in Automation For Jira. You'll have to do that mark manually right now. 

Hi @Mathieu Marcoux , Please refer to this post: https://community.atlassian.com/t5/Jira-Software-questions/Is-the-new-Jira-Deployments-feature-configurable-with-Github/qaq-p/1511611?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_question&utm_content=topic

Hi Chares - Welcome to the Atlassian Community! Please see this post: https://community.atlassian.com/t5/Jira-Software-questions/Is-the-new-Jira-Deployments-feature-configurable-with-Github/qaq-p/1511611?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_question&utm_content=topic

Hi @broberts - Modify the Field Configuration for the project to remove the Resolution field as being required. 

Hi Saeed - Welcome to the Atlassian Community! I had that happen a few minutes ago, too. I ended up opening up another browser window and it worked fine. Not sure if it was just a temporary glitch or what it was. Try that and see if it works now. 

Hi @Константин Смирнов - Welcome to the Atlassian Community! The first question would be, Why do you have so many issues on a single board? That is unmanageable for a team. I would suggest you reduce the number of cards on the board - maybe by creating additional boards. If several are done, they they should be released…

Hi Prashant - Welcome to the Atlassian Community! Can you share the rule you have so far? I assume you are tying to do a Condition? And do not see the field you want?

Hi Ally, Have you followed the guidance in this document? https://support.atlassian.com/jira-core-cloud/docs/configure-field-layout-in-the-issue-view/ And if so and it still doesn't work, I would open a support ticket with Atlassian: https://support.atlassian.com/contact/#/

1. Go to Project Settings 2. Click on Summary 3. Click on the top link under the Screens section. This is the current Issue Type Screen Scheme. 4. Click on the Actions button in the top right and select Use a different scheme. 5. Search for and select your new Issue Type Screen Scheme. 6. Click Associate button. You should…

That is a really strange message to present for a license issue. But hopefully they will help you get it sorted out. 

That's very strange. I would go ahead and submit a support ticket to Atlassian to see if they can help you figure it out. https://support.atlassian.com/contact/#/ Then please post back here whatever the resolution is. 

Is there anything else we can help you with on this post? 

You are very welcome! Thanks for diving into the community and asking questions!

@PhilSpo also looks like there is this format: {{issue.resolutiondate.asLongDateTime}} You might drive the as in front of LongDate. Also see Andreas's suggestion below. 

Hi Silvia, Plans, i.e. Advanced Roadmaps, are only available for Premium subscriptions. You can determine which subscription you have by following Joel's guidance in his answer. 

Hi Cédric, Personally, I think you are going to a lot of trouble to try to implement something that is going to be very cumbersome and will never work the way you want it to. Automation already has some really good built in features to handle connections between issues using the linked issues functionality. Although it…

Hi @Tomislav Hrelja - Welcome to the Atlassian Community! There's no real way to implement additional hierarchy in a non-premium subscription. And then, it is only somewhat possible using Advanced Roadmaps. And even then, the process is to create a new Issue Type at the Task/Story level and then use issue links to create…

Hey @Larry Wilson - thanks for the update - can you describe a little more how the license limited the data or access to the project?

Oi julio, Os campos personalizados criados em projetos de próxima geração estão disponíveis apenas para esse projeto. Você não os encontrará nos campos personalizados compartilhados. A propósito, roteiros agora estão disponíveis para todos os tipos de projetos, não apenas para projetos de próxima geração. Portanto, você…

Hi Frank - Welcome to the Atlassian Community! The reality, I am afraid, is that you are not going to be able to talk directly with anyone. You can do some training as @Liam Green suggests, and/or continue to post questions here in the community to help you along. 

Hi Charlotta, If you are just modifying the workflow to add a transition screen, it will not break anything at all with the existing data. It will not update existing resolutions. It will effect all tickets that use that workflow, regardless of the project. I hope that helps!

Hola @Fflores : ¡Bienvenido a la comunidad de Atlassian! Desafortunadamente, no puede comparar dos campos de fecha usando JQL en un filtro. Puede comparar un campo de fecha con una fecha real, pero no con otro campo de fecha en sí. Sin embargo, probablemente podría escribir una Regla en Automatización para Jira para…

Hi Gui, Be careful about changing status names because it will change it everywhere in your system, not just in that one workflow. That might be what you want, and if so, then good. But just be aware. Once you made the change and the users refresh their screen, do they now see the new name?