Trudy P Claspill Community Champion

Comments

  • Hello Maya, Use the Sprint Started trigger. You'll have to select the board where you want this to take effect. Then use For Branch / Related Issues / Issues in Sprint. Does your sprint have issue in it from more than one project? If so, you will need to create a Global Rule and set the scope for the rule and this step to…
  • Hello @Mia Nguyen Welcome to the Atlassian community. Make a copy of that workflow, modify the copy, and assign the copy to a workflow scheme for the desired project.
  • Hello @Thiago C Welcome to the Atlassian community! Unfortunately there is no way to recover a deleted board. A Sprint is created within a board, but may be displayed in multiple boards. Boards display issue based on the board filter. If there is an issue within scope of the board filter (Board A) and the issue is assigned…
  • Hallo, Benutzerdefinierte Felder, die in teamverwalteten Projekten erstellt wurden, können derzeit nicht mit anderen Projekten geteilt werden. Dazu gibt es hier einen Änderungswunsch: https://jira.atlassian.com/browse/JSWCLOUD-20905 Benutzerdefinierte Felder, die für vom Unternehmen verwaltete Projekte erstellt wurden…
  • Hello @Ulric Yearwood Welcome to the Atlassian community! Are you talking about the underlying filter for the board, which selects the issues to include in the board? Or are you talking about the quick/custom filters that appear above the board? Quick Filters from a board for a Company Managed project: Custom Filters from…
  • Hello @nrasmuson Welcome to the Atlassian community! Please tell us specifically how the results of the two gadgets are different. The pie chart appears to be selecting 25 issues, recognizing that 14 issues have the Unplanned Work component, 3 have the Maintenance component, and 8 have no component value at all. We can't…
  • Being new to Jira you might find value in taking some of the self paced courses available from the Atlassian University. They have a variety of courses for different experience levels.
  • Ah, yes. There is that box in the Trigger that can constrain the action to only issues that have changed. Let us know if that solves your issue.
  • Hello @Rui Nian From the General settings of your board you can click on the "Edit Filter Query" link (shown near the top of the image I provided). That will take you to the Issue Search screen where you can edit the filter and save it. Once edited and saved, the board will automatically use the changed filter. To get…
  • Hello @Vera Valshonok No, there is no functionality to share configurations between Team Managed projects. The nature of Team Managed projects are that they are stand-alone and customizations in them don't affect any other project. You will have to manually recreate the items in the new project.
  • Hello @Sreenadh Yes, there are limitations. For a Free subscription you are limited to 100 emails per day as per this document. That is counting all emails sent by your system whether then are normal project notifications or emails from an Automation rule. That same limit is mentioned in this document that is specifically…
  • Hello @Amy Conley What is the error you are receiving? How many people have you tried to add to the Requestor field criteria? Can you show us the actual syntax of the filter you have created when you receive the error? It is okay to obscure the actual values, but make sure we can see all the punctuation.
  • Hello @[deleted] Welcome to the Atlassian community! Did you create a Team Managed or a Company Managed Work Management project? That information will show at the bottom of the navigation panel on the left. If you created a Company Managed project, then when you create a new Work Management project you can elect to share…
  • Hello @Rui Nian Welcome to the Atlassian community! You said you "created a general Board in my "General" project". You also said "when I navigate to the sprint board, the task is not visible" after assigning "the task" to a sprint. Is the "sprint board" in that second statement the same as the "general Board" in the first…
  • Hello @tracey.fudge Welcome to the Atlassian community! When you say "it didn't work" do you mean the JQL doesn't give you the right set of issues or the rule doesn't do what you want? If the problem is the JQL, please provide the details of an example of an issue that you expected the result to include (or not included).…
  • Hello @sanam khan Welcome to the Atlassian community! In a Scrum Backlog screen the list of issues are grouped by the sprint (Active or Future) to which they are assigned. If they are not assigned to an Active or Future sprint and are not already completed then they appear at the bottom of the screen in the Backlog list.…
  • Hello @MALIGEAY Welcome to the community. Currently it is not possible to create Priority Schemes per project in Jira Cloud using the built-in Priority field. There are two change requests for that here: https://jira.atlassian.com/browse/JSWCLOUD-21455 https://jira.atlassian.com/browse/JRACLOUD-3821 One alternative is to…
  • Hello @Robert Bojarski Welcome to the Atlassian community! According to this document: https://support.atlassian.com/organization-administration/docs/delete-your-organization/ "How long will it take? Removing products from your organization can take several weeks. To reduce the risk of accidental data loss, products aren’t…
  • Hello @David Pleşu When you make a field mandatory through a Workflow Validator then you are telling the Jira the field cannot be left empty. Trying to set it to None is the same as telling Jira the field is empty. These are contradictory requirements. Also note that the Epic Link field is valid only for standard issues…
  • Hello @Kavi What is the trigger for these rules? Is it using the "Issue Created" trigger? I would recommend putting an Issue Fields Condition after the trigger of each rule so that each rule will run only when the create issue is NOT ONE OF the projects handled in the other rule.
  • I'm glad we were able to find a solution. If your questions have been answered and your problem solved, please consider marking the Answer as Accepted to help other users find validated solutions.
  • I don't believe that is possible. The screen you present during a workflow transition is for updating the issue being transitioned. You might be able to use a workflow Post Function to create an issue, with the help of a third party app. Or, if all the minimum required information for the new issue is contained in the…
  • What error? The last response I see is in your conversation with @Mark Segall you said you were going to try his suggestions. Have you tried them? Where are you getting an error? What is the error? Is the rule executing? Can you share the audit log?
  • In that case I would recommend that you look at portfolio/project management tools. There are several available from the Atlassian Marketplace. Or if you are willing to upgrade to the Premium plan you can get the Advanced Roadmaps feature built into Jira.
  • By adding a custom field that you populate with an Automation Rule, you would be able to build a filter based on that custom field and use that filter with several of the natively available dashboard gadgets. With the Automation Rule, you would be updating the issue in real time by creating one or more rules that would…
  • Is it only the issues from the above automation that you want automatically added to the Active Sprint? Does the Scrum Board have more than one active sprint at a time? In the Clone action you can choose to set the Sprint field for the new issue. You will be allowed to select the "Active Sprint" or "Next Sprint" for a…
  • This documentation provides guidance on using the CSV import feature. https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/ Note that import process does not support importing History (i.e. changes of status) for an issue, but status history can be imported using the JSON import format.…
  • Is the problem that the issue needs to stay in the status it starts in? If you need it to stay in the status the you create a self reflecting transition, where the From and To status are the same. You can then attach the screen to that looping transition.
  • You should not need to use the Advanced JSON Editing option. You should be able to simply select the field using the Choose fields to set option. You can then insert the smart value as the value you want to save in the field. {{issue.status}} will save the unique numeric ID associated with the Status value.…
  • Hello @Dirk-Jan Dijkman Welcome to the Atlassian Community! As per this documentation concerning parent issues (i.e. Epics) "Parent issues on your roadmap's timeline are scheduled using the Start date and Due date, regardless of whether you’re planning for scrum or kanban teams." It further states that if the fields are…