John Funk Community Champion

Hi Liz - It sounds like you might have a free account which does not provide support. Another thought - you said your query turned up 136 issues for the board at the time. How many of those were Done? It might be that some dropped off the board. 

You might try just as a test: Create a custom single line text field and copy in the Key for a a handful of issues. Then use the new custom field as one of the axis and see what you get. :-)

Hey Emily, Try using this: {{#lookupIssues}} * <a href="{{url}}">{{key}}</a>] {{issue.priority}} | {{issue.created}} | {{issue.status}} {{/}}

Hi @mdangear , You need to change the permission scheme and modify who can browse project.

Затем вы можете использовать функцию безопасности уровня проблемы. Вы можете прочитать больше об этом здесь: https://confluence.atlassian.com/adminjiracloud/configuring-issue-level-security-776636711.html

Was thinking you might could do it with a Dashboard and Issue Statistics gadget but that wouldn't work if multiples can be in the same project. 

Hi Baraa - do you need more assistance with this?

Hi @parvathavardhini - Welcome to the Atlassian Community! Typically, you have to be a member of a group to be able to assign access to that group. Add yourself to one of the groups and see if it shows up for your to grant Access to that group. 

Hi Ginevra, That sounds like a permission problem. Make sure that you have Browse Project permissions for Project B. 

Je suis désolé, mais je ne trouve pas ce nom de ce champ.

Hi Pascal - Welcome to the Atlassian Community! Can you explain more of what you are trying to do? Maybe with an exact example? 

Hi Brooke, I am wondering if you might be able to create a Dashboard and add a Two Dimensional Issues gadget to it. Then use Key for one axis and [client name] for the other axis. Not sure if that would give you want you want or not.

The problem is that Next-gen projects are not currently setup for Automation for Jira to handle Epics on those types of projects. That's probably why it works sometimes and not others. 

Hi Michael, Not sure how you can do that right off hand. But one question - could the same Serial# appear more than once in the same project?

Привет александр, Вы не можете скрыть некоторые поля от некоторых пользователей, но показать другим пользователям все поля для карты. Вы можете контролировать, какие поля можно обновлять или нет, но нельзя скрывать значения в них только от определенных людей.

Should this rule execute against a single project or globally? Or just a few projects? When you say that it only works against the same workflow that tends to tell me it is running against projects that it should not. What are the exact conditions it should run against? In other words, against which Projects should it run?

Bonjour Carole - Bienvenue dans la communauté Atlassian! Avez-vous une capture d'écran du Web sur laquelle vous avez besoin d'informations? Je ne sais pas exactement de quel champ il s'agit.

Great - I am glad you were able to get to a good solution. :-) And thank you for the additional information. Did you end up also giving them Service Desk Team role? 

So you need to create 3 new contexts - one for Bug, one for Test-case and one for Story. Only put in the options you want for each one of those issue types. To create the new contexts, click on the Add new context link at the top. 

HI Tina, My two cents is that personal WIP Limits are for personal boards and should not be a part of a Team Kanban board. WIP limits (the Max number) are for the column and everyone on the team working in that column and should not be setup by individual. 

Sorry, Xray is not something I work with or have knowledge about. :-(

¡Excelente! ¡Buena suerte! Saludos!

Hi @Siobhan Kelleher - Welcome to the Atlassian Community! If it's not there, there's probably no hope of it being added in the short term. You would probably need to contact Atlassian Support to ask about it. https://support.atlassian.com/contact/#/ In the short term, you could create a new custom field with the three…

Hi Aroldo - Welcome to the Atlassian Community! Just a note that you cannot create Next-gen projects with shared configuration. You must create each Next-gen project independently. But Mathieu's guidance works great for Classic Software and Jira Service Desk projects. 

Great!

Can you share a full page screenshot of the Context page for that custom field? 

Go to Project Settings > Then select Issue Types on the left hand menu. :-)

Você não pode fazer campos em cascata separados no Jira Cloud. Você pode criar um novo campo personalizado da lista de seleção (em cascata). Mas será um único campo com um único nome, não dois nomes.

Hi and Welcome Anna! We are glad you are here!!

Ah, the deployment type above on this post said you were using Cloud. For Server, Automation for Jira is an add-on/plug-in. There is a limited but Free version called Automation For Jira Lite or a fully functioning paid version which is just Automation For Jira. See this document for the comparison of the two products:…