Comments
-
What type of project is this - Next-gen or Classic Software?
-
Hi @Jerome Ortega and @antony.nelson Try it without the uppercase T, so {{issuetype.name}}
-
Hi Jim - Welcome to the Atlassian Community! There appears to be an active incident being worked on. You can follow along here: https://jira-software.status.atlassian.com/
-
Hi David - it looks like there is an active incident being worked. You can follow along here: https://jira-software.status.atlassian.com/
-
That's very strange because fields are not associated with users at all. Maybe try to clear your browser cache and history and try again. Or even try a different browser.
-
Hi @Егоров Виктор , I don't know if this helps or not, but this is what I use: {{issue.key}}'s {{fieldChange.field}} field was updated from {{fieldChange.fromString}} to {{fieldChange.toString}} by {{initiator.displayName}}.
-
Sorry, I understand better now. No, the labels field is not available using the lookupIssue function. See the document for the list of available fields under the section on lookupIssue: https://support.atlassian.com/jira-software-cloud/docs/automation-actions/
-
Привет @Екатерина Соловьева - Добро пожаловать в сообщество Atlassian! Это проекты следующего поколения или проекты классического программного обеспечения? Для классического программного обеспечения следует изменять только имена созданных настраиваемых полей, а не системные поля. Чтобы перейти к настраиваемым полям,…
-
いいえ、最初に元のプロジェクトを削除しない限り、同じキーを使用することはできません。ただし、移行を行うと、新しいキーを持つカードと古いキーの間にリンクがあるため、古いキーを再利用することはできません。 :-(
-
WOW, thanks for the insight, @Daniel Eads !!
-
While on the Create screen, can you click on the Configure fields button? And from there, can you click on the Where's my field button?
-
Hi Dries - No, that is currently not possible. You must be the owner of the filter to be able to change it. There is an open feature request that is currently being worked on to provide the ability for multiple people to be able to edit the same filter though.
-
That should definitely work - can you share some screenshots? You can also try: project in ("LSP Sustainment", "The Time and Attendance Project - Tech") AND issuetype = Epic
-
Hi Diana - Welcome to the Atlassian Community! Try this: (project = "LSP Sustainment" OR project = "The Time and Attendance Project - Tech") AND issuetype = Epic
-
Hi Seema, When you say you are unable to add the column - what error are you getting or what problem are you having? What happens when you click on the Add Column button? And are you a Project Administrator for this project?
-
You should probably open a ticket with support then and see what they say. https://support.atlassian.com/contact/#/ Post the resolution back here please, so we can close it out. Thanks!
-
Salut Eric - Bienvenue dans la communauté Atlassian! Vous aurez besoin d'un module complémentaire tel que Deep Clone pour pouvoir cloner des commentaires.
-
You can try this also if you still want to exclude those components: project = MIP AND (component not in ("PRO SERVICES ADMIN") or component is empty) ORDER BY key ASC
-
Hi Jerome, This was in the document you link to above: {{issueType}} - Returns the issue type Have you tried that syntax?
-
The labels field is a universally available field with the same values showing for every project. So I am confused now as to the question as there are not separate values in the labels field that are associated with certain users. Can you provide more details?
-
Hi Sara - Welcome to the Atlassian Community! It might be that the field is now showing if it is empty. Got to Project Settings > Issue layout and check the bottom section for fields hidden when empty.
-
And if you just run that query as a filter you get a lot more issues than you see on the board? Can you verify that all of the statuses showing in the filter are mapped to a column on the board?
-
Hi Mike - Welcome to the Atlassian Community! Currently that is not possible. There is an open request that you can vote for and follow here: https://jira.atlassian.com/browse/JSWCLOUD-17499
-
Hi Prabhu - Welcome to the Atlassian Community! Jira will only consider the issue as Done/Closed if it is in the last column on the sprint board. So whatever status you consider to be "closed", then that status needs to be in the last column on the board.
-
@Alfred Pullicino - You probably need to submit a support ticket. I also have the same problem. Please post back here with any resolution. Thanks! https://support.atlassian.com/contact/#/
-
Is this labels field a custom field that you created in a Next-gen project? How many different labels fields are you using?
-
I would go ahead and submit a support request with Atlassian: https://support.atlassian.com/contact/#/ Please post back here with the Resolution so we can close this one out. Thanks!
-
But not all of the Epics for that project show on the board? Can you share the filter that is being used for the board? Also any Sub-filters?
-
Hi Morten - Welcome to the Atlassian Community! I am not sure if there are any sample projects that come with the initial setup or not. If you go to Projects - View all projects, do you see any? Otherwise, I would just suggest you create a new project and play with it. You can delete it if you don't like it or it doesn't…
-
Can you show me screenshots of that? Because I just had someone in our organization that has only site-admin permissions and not administrator permissions try to get to the Settings > Issues functionality and they could not.