Comments
-
Post-functions are for things you want done after the transition has already been completed. You can't use those to prevent a transition. You would need this Condition to be in the workflow that applies to the issue types where sub-tasks can be added as child issues, i.e. you can create Sub-tasks under a Story so apply the…
-
Hello @Lori Milam You can find the link also from the Your Work > Boards option.
-
Hello @Mercker, Jeramie Welcome to the Atlassian community. Are the issues in a Company Managed project or a Team Managed project? @Stefan Salzl 's answer applies if the issues are in a Company Managed project.
-
Hello Steve, When you are editing the workflow and click on the transition to Done you should get an option to view the Triggers, Conditions, Validators, and Post Functions associated with that transition. Do you get that? Then click on the option to view the Conditions. Then click on the option to Add a Condition. You…
-
Glad I could help. If your problem has been satisfactorily addressed, please consider marking the Answer as Accepted.
-
The short answer is a qualified "no", you can't get everything you want within the automation rule. There is an Issue Transitioned trigger for Automation rules. However... 1. The trigger can't be configured to recognize a self-reflecting transition. You would either 1a. need multiple rules with unique triggers for "issue…
-
Hello @Jack_Marquez If a backup of the workflow was not made then there is no way to "restore" it. You can manually modify the existing workflow to take it back to what it was like before. If it truly was a default workflow you can create another project from the same project template, and then take the default workflow…
-
In one Edit action you can edit more than one field. Just select additional fields to edit.
-
Hello @Antony Delgado There is not a single solution that can be used to determine usage of any app. If there isn't something like using an issue filter to determine if there is data in issues related to the app, then your best bet is to contact each app's vendor directly to find out if they can advise you on how to…
-
Hello @Vijay dumpala Can you provide more details? Do you have any Quick Filters activated on the board? Can you provide screen images to illustrate the problem? Can you show us the board? Can you show us a list of the Active Sprints? Can you show an image of an issue that you think should be shown but is not? What is the…
-
Hello @Starflix LT Welcome to the Atlassian Team. It is not enough for a user to appear in the User list. The user has to be a member of a group that is listed in the Product Access area for the Product to which you want them to have access.
-
Hello @Daniel Bermudez No, there are no permissions specific to enabling or disabling the Reports feature, so there is no native way to hide that for specific users/roles.
-
In the basic Timeline feature you can see that the Feature issue type is considered a child issue of the Epic. In the basic Timeline feature you can display the time bars for child issues using either the Start date and Due date fields, or you can display the time bars for child issues based on the Sprints to which they…
-
Please show the details of the Edit Issue step in the above rule. Please show the Audit Log information for execution of the above rule. Have you changed the scope of the above rule to be multiple-projects, as I described? The Edit will not work if the scope of the rule has not been changed. Please show use the Rule…
-
Hello @Angana Patel If you are referring to the Timeline feature available in the left-side navigation panel for a board, it is not possible to add more fields to the display of that feature, nor change the time bars to use different fields. The time bars are locked into using the Start date and Due date fields.
-
Hello @Josh Leggatt Welcome to the Atlassian community. Can you show us the screen where you are clicking something to "view the queue" and point out what you are clicking on to view the queue? And then please show us the screen that actually displays.
-
You have changed the rule so that the Edit is no longer being applied to the "For: Linked Issues" branch. That was not part of the solution I described. The Edit needs to remain contained within the "For: Linked Issues" branch. The solution, with your original rule, is to change the rule scope.
-
Hello @Kristmundur Gudmundsson Can you provide more information about what you mean by "security container"? Are you following guidance from some online document? Can you provide a link to that document?
-
Hello @Phil I suspect that the answer is "You can't do that", but I'm not finding a screen with quite the same text on it that you mentioned. Exactly how are you getting to that screen? Can you provide a screen image? How did you "delegate" project creation?
-
Ah, yes, sorry. There are single-project scoped rules and multiple-project scoped rules. With a single-project scoped rule you are allowed to Clone an issue into a different project, but you cannot then use or operate against the issues in that other project. The rule needs to be changed to a multiple-project rule and each…
-
Hello @Ankush Gautam Welcome to the Atlassian community. Are you able to create the dashboard with no shares? How do you know you have the global permission to share filters and dashboards? Global permissions are allocated to user groups. How have you confirmed that you are a member of a group that has been granted that…
-
Hello @Peggy Burns Has your site been changed from the Original user management model to the new Centralized User Management model? Have you reviewed the roles/groups to which the user is assigned? https://support.atlassian.com/user-management/docs/give-users-admin-permissions/
-
Hello @Charles Lindsay Before implementing that change I recommend you dig into discovering what problem the user is trying to solve with that solution. The Sprint field specifically cannot be exactly duplicated, as it is a unique field type that Jira does not make available to be used as the field type for additional…
-
Hello @Mary Mark If you want to Clone the issue into multiple projects you will have to add a Clone Issue action for each project to which you want to Clone the issue. To concatenate two values into one field you will need to set the destination field using smart values. This page shows functions that you can use in smart…
-
Hello @Kaitlin Gatti Can you show us a screen image of the filter you created? When you try to view queues, what exactly happens? Can you provide a screen image of what you see? Is this only for issues created in Jira Service Management projects from emails? Or is it for issues created for other projects, and/or for issues…
-
@Yvonne Do you mean that when you log time against a Sub-task then you want to still update the Story that the sub-task's parent is linked to? Is the Remaining Estimate of the sub-task's parent being updated automatically when you log work against the sub-task?
-
That suggests that the board where the sprint was created has been deleted. At this point I suggest that you contact Atlassian Support for more assistance. https://support.atlassian.com/contact/#/ You could use the REST API to get the sprint's information, which includes the board ID for the board where it was created.…
-
@adithya Take a look at the Cumulative Flow Diagram. https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-cumulative-flow-diagram/
-
Can you do a search for "sprint =" that sprint's name and confirm there are not multiple sprints with the same name? When you start typing in the sprint name you should see a list of possible matches: Can you show us a sprint report for that sprint that confirms that it is not open / is closed? Example:
-
At this location ...insert a Lookup Issues action. Remaining Estimate is stored as seconds. So if you want to set Due date to now() plus the remaining estimate sum of the Epic's child issues (found in the Lookup Issues action) then use this smart value: {{now.plusSeconds(lookupIssues.Remaining Estimate.sum)}}