Comments
-
I would not recommend using the Description field because searching based on text and relying on users to enter the correct text is unreliable. You could use a Label value. Label values are globally available, not case sensitive, and not defined per project, so that is a reasonable option. But again, you are going to be…
-
So, your criteria are: 1. The issue is in the "backlog" column 2. The issue is displayed in the Board view of a Scrum board, which means it is in an Active Sprint 3. The issue has not been updated for 6 months or longer. In that case the filter you would need is: status in (<backlog>) and sprint in openSprints() and…
-
Hello @Martin Rady Welcome to the Atlassian community. Issues exist in one and only one Jira project at a time. The issues that you want to include can't exist in the teams' Projects and another "coverall" Project at the same time. How do you identify the issues in the other teams' Projects that apply to your "project"? If…
-
Hello Meghana, Thank you for that additional information. Are you working with issues in a Team Managed project or a Company Managed project? You can get that information from the Type column on the View All Projects page under the Projects menu. Can you provide a screen image of what you are viewing when you are referring…
-
No, it is not possible to get on a call. I do not offer live telephone support. I'm just another user of the products trying to help answer questions. To add a status to a workflow in a Team Managed project you need to: 1. Go to Project Settings 2. Select Issue Types 3. Select a specific issue type from the list 4. Click…
-
I'm glad you were able to work it out. Please consider clicking on the Accept Answer button to mark your question as Solved.
-
What is shown in the History for the newly created sub-task? Are there multiple entries for setting the Assignee field? Sometimes rules that have been edited many times can end up not functioning correctly. Have you tried recreating the rule from scratch? Also, you should be able to use a For Branch to shift focus to the…
-
Adding to this... The filter used by the summary board of a JWM project is project=ABC and (statusCategory!=Done or )statusCategory=Done and statusCategoryChangedDate <-2w)) The summary page is designed to show only issue on the companion board, and the board is hard code to show only not "done" issues and issues that have…
-
Hello @Jagrut Sharma Welcome to the Atlassian community. With what type of project are you working? You can get that information from the Type column on the View All Projects page under the Projects menu. Can you show us the screen in Settings that you are viewing where you are trying to add a new status?
-
Obrigado por compartilhar essa informação. Se você puder visualizar o problema com um link direto, verá o status atual do problema no canto superior direito. Para que um problema fique visível no quadro, ele deve primeiro estar dentro do escopo do filtro do quadro. Você pode revisar o filtro usado pelo conselho e confirmar…
-
Hello @[deleted] Welcome to the Atlassian community. With what type of project are you working? You can get that information from the Type column on the View All Projects page under the Projects menu. Can you provide a screen image of what you are viewing? And can you indicate in that image where you are trying to move…
-
Hello @Meghana kamble You can learn more about creating filters here: https://support.atlassian.com/jira-software-cloud/docs/search-for-issues-in-jira/ How are you evaluating that the issues are more than 6 months old? Is that based on the date they were created? Are you working with a Team Managed project or a Company…
-
Olá @Tiago Chevalier Existem várias razões possíveis para isso. Primeiro precisamos de algumas informações adicionais. Em que tipo de projeto os problemas estão contidos? Você pode encontrar as informações do tipo de projeto na página Exibir todos os projetos no menu de projetos. Que tipo de quadro você está visualizando?…
-
Hello @Dimple Welcome to the Atlassian community. It is not possible to change the hierarchy levels in that manner with native functionality. The native hierarchy of Jira is Epic |-- standard level issue types (i.e. Task, Story, Bug) |-- sub-task level issue types It is not possible to insert a level between "standard" and…
-
Hello @Mike Thomas Please show us how you have changed the filter when you tried to add the In Progress status to it, and the JQL errors that you got. We can't determine what you may have done wrong without that information. You should be able to add more statuses by making a comma separated list between the parentheses:…
-
Hello @_string_ I believe this would work: issuekey in childIssuesOf("EX-000") ...where EX-000 is the issue key of your Epic.
-
Issues are not "in" boards. Boards are based on filters, so an issue can be visible through multiple boards simultaneously. When you are viewing/editing an issue there is no specific link between that view/edit screen and a board from which you may have opened that screen. So there is no method to use the board currently…
-
Hello @Jan-Christopher Lietsche Based on the image you provided, is the highlighted issue the Capability? And is the issue that is being viewed in that image a Bug that has been linked to the Capability? If you are using generic issue linking (the linking that is shown in that image) the reporting capabilities are limited…
-
What is shown in the History for the newly created sub-task? Are there multiple entries for setting the Assignee field? Prior to the Create Issue step can you add a Log action step, and in that step print the value in the Tester- field into the Audit Log? Use the smart value {{triggerIssue.Tester-}} Then run the rule again…
-
Hello @Maria Savignano Looking at just the second rule image you provided: Trigger: the value for Responsible Area is changed Condition: Project = DID Condition: There are linked incidents present: Types: is part of Branch: For Linked incidents Types: is part of Edit incident fields First I would recommend that you might…
-
Hello @Leyla Kinaze After changing the value in the issue, and prior to sending the Slack message, you need to add a Re-fetch issue data action. https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Re-fetch-issue-data
-
Regarding the fields you can select from to add to the card, that list should show you the fields that are available to the issue types in your project. It may be limited to the fields that you have added to the Edit/View screens (or the Issue Layout) - I have not fully tested if that is a limitation. Is the Story points…
-
Olá Adriano, Nesse ponto da criação do plano, você seleciona o site de origem e o site de destino, e não os projetos individuais que deseja migrar. E permite selecionar um site com assinatura gratuita. Testei essa etapa com meu próprio site Jira, que tem uma assinatura gratuita. A seleção dos projetos acontece na próxima…
-
Hello @Inger Marie Jakobsen As per this document: https://support.atlassian.com/jira-software-cloud/docs/search-for-advanced-roadmaps-custom-fields-in-jql/ ... you can use this JQL: issuekey in portfolioChildIssuesOf("INIT-001") Where INIT-001 is the issue key for the Feature. That will give you all the Epics, children of…
-
@Mohammed Yousuf Your JQL statement is incomplete.
-
Hello @Leyla Kinaze Welcome to the Atlassian community. What mechanism are you using to change the priority value? Is that a workflow Post Function or perhaps an Automation Rule? What mechanism are you using to send the notifications? Is that coming from the built in Notification configuration, or is that coming from a…
-
Hello @TP It is not currently possible to increment a variable in a branch. That change request is included in this change request, to which you can add your vote: https://jira.atlassian.com/browse/AUTO-26
-
Refer to https://status.atlassian.com/ It took Atlassian some time to update the page, but as of about 40 minutes ago they got it updated to show most Cloud products experiencing an Active Incident.
-
It took Atlassian some time to update their status page (https://status.atlassian.com/), but as of about 27 minutes ago they got it updated to show most Cloud products experiencing an Active Incident.
-
Refer to https://status.atlassian.com/ It took Atlassian some time to update the page, but as of about 27 minutes ago they got it updated to show most Cloud products experiencing an Active Incident.