Bill Sheboy Expert

Hi @Rhys Hill I am glad that you got this working. Unfortunately, you cannot nest branches in automation rules or store temporary variables, so your approach of cascading the Epic Link works... The other approach I have used is multiple rules to update the different levels, using a common triggering event (such as a…

I liked the response to item (2), until... Perhaps this is just semantics; I find troubling the phrase "claim the entire # of points as they’ve completed their work". Yes, given the way the team appears to support this value stream, they have finished some steps...and some steps remain to release to production. So the…

Hi @Rhys Hill Yes, that sounds possible. Maybe try this: * Trigger is due date change * Probable should add a condition to ensure the source was an edit, and to confirm your issue type * Add a branch to iterate over the children, either as sub-tasks or using JQL * Set the due date as you note Please see this reference for…

Hi @SWAPNIL SRIVASTAV Using the JIRA automation rules, it is possible to trigger a rule when an issue is deleted. Regarding 2 automation triggers, some of the triggers support multiple values, but there does not appear to be a way to have two different triggers. As a work-around, you could: * Create a rule for your first…

Hi @Eugene Stavast -- Welcome to the Atlassian community. What problem are you trying to solve by reporting on the child issues? Best regards, Bill

Hi @Kara Nadarajah Depending on your pipeline, the answer is probably yes. If you don't have an automated pipeline, you could run a scheduled rule once per day (or run it manually), look for new "done" things, create a version, and then assign the items to the version. If you are using something like GitHub, you can use a…

Hi @Graham Harbour The value you want is: {{issue.project.name}} For stuff like this which is not listed in the Smart Value documentation, try this info to do a REST API call for an example issue: https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/ Best regards, Bill

Hi @Emily Lukasik Try this one to produce a bulleted list of the values with the key hyperlinked: Here is the list: {{#lookupIssues}} * <a href="{{url}}">{{key}}</a> {{/}} Best regards, Bill

Hi @michael.chase -- Welcome to the Atlassian community! A board is a filtered view of a backlog (project). Check the filters for the two boards, and update them to match what makes the issues on the different boards. For example, it could be by Epic or Component, or Label, etc. The issues should reflect that difference…

Hi @Jason J. Fedelem We do that to put static text in the description. As long as your team members know how to edit a table in the mark-up it will work. Below is an example table to insert with an automation rule: ||column heading A||column heading B|| |row 1, column A data|row 1, column B data| |row 2, column A data|row…

Nope. I tried with and without source actions (e.g. Edit) and the rule never fired. I even tried Move to see if Convert To... was considered a different path, and that didn't help. __Bill

Hi @Gregg Humerickhouse -- Welcome to the Atlassian community! Looks like this issue is an open defect, which you may review and vote for here: https://jira.atlassian.com/browse/JRACLOUD-72289 Here is another posting with some ideas about…

Hi @hanna.podoliak -- Welcome to the Atlassian community! To save you some experimentation time, I tried this with automation rules and it does not work. The rules cannot detect an Issue Type change when the source is a Convert To... trigger. We are submitting a defect to Atlassian for this problem. Best regards, Bill

Hi, and thanks for this discussion. One better approach to handle delivery is to: split work into small, valuable, similar-sized chunks; count the chunks; and determine progress by paying attention and adjusting as you go, while improving your experience and skills. However...Sometimes teams decide to forecast effort and…

Hi @PhilSpo Would you please explain the problem you are trying to solve? It seems you want to track development time keeping and a separate measure of people's "value" or "worth". What are you gonna do with that second measure? Best regards, Bill

Hi @Ron Saavedra Reading your follow-up posting, about notifying when issues are added to the sprint... Have you tried to trigger on a change to the sprint field, and then use JQL to filter and detect if the sprint is in opensprints()? At an issue level, you could then send the notifications for added items. Best regards,…

Hi Myron, For bulk edit, I believe the other post was suggesting updating the old item status values to work-around the reporting issue. As an alternative, you could just leave those alone, remembering what the values previously were, and move forward from there. Best regards, Bill

Hi Sam, Here is an outline of an Excel approach. Please adjust based on what you want. For example, what do you mean by "% complete"? * First, make a query with the data/project you want to consider, including all issue types * Export this data, and put it in a spreadsheet tab/worksheet. Let's call this tab JIRA. * Sort…

Hi @Tushar A. When I tried your smart values alone, they worked for me. Although I would add the issue. prefix to reduce confusion for others reading the rule. Maybe there is a problem with your table mark-up, so try to implement it piece by piece to see what is causing the problem Best regards, Bill

Yup; {{sprint.startDate}} Look here for more info on the available smart value attributes: https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/ If this ended up helping you, please mark this thread as answered so others can find it too. Thanks!

Thanks for the updated images. Your rules say to only update the Start Date when it wasn't empty. Same for Due Date. Is that what you want to do: only replace the dates, not set them when empty?

Hi @Rich Moll Epic Link is one of those fields which only displays on the view page once it has a value. Do you have an example where the story/bug has an assigned Epic Link, but does not display? Best regards, Bill

Hi @Clark Everson Looking at your rules, the actions are listed after the branch, not inside it. Note the plus sign to add a component to the branch under its tree. Try to re-add your components (the edits) and then delete the ones after the branch. Best regards, Bill

Hi, and thanks for clarifying. So... * When the Parent Due Date changes... * Check if an existing comment exists, you calculate the difference, in order to... * Update the children's Due Dates by that difference amount * And save the latest Parent Due Date in a comment to refresh it Correct? First thing, I wouldn't use a…

Hi @justin romeo -- Welcome to the Atlassian community! Short answer: probably yes. Longer answer: Can you give more details on the expected flow of your rule? If the parent is the thing triggering, you can use {{triggerissue.duedate}} If you are triggering from a child changing, moving up to the parent, and then back down…

Yes, and... You could use the Priority field, making your process to reserve the Highest value for only your top items, and then filter on that field/value. If you are already using all of the available Priority values, consider adding a new value for this indication. Best regards, Bill

Hi @Ron Saavedra Looking at community posts as recent as Sept 2019, it doesn't appear that the sprint state is accessible yet. Please look in this documentation, searching the page for Sprint, to see what is available: https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/ Best regards, Bill

Hi @Alex Unwin Although this probably should not fail silently, it does seem like a permissions issue. Changing the Epic Link is an edit action, and if the requestor does not have edit permission for the scope of the created issue, it will fail. Please check the edit permission for the user. You could try to use the…

Thanks for the information. For the individual issue that should have moved to Done, what do you see in the item's activity log? Does it indicate the automation ran? Does it indicate the item moved to Done? If neither happened, please consider adding the suggested logging to better see what is happening.

Hi @Brett Dains One way to do this is with 2 rules: * Trigger as you did with a sub-task's components changing, and then clear the Parent's component * Trigger on parent's component change cleared by automation, branch to re-add all of the sub-tasks values. Set the option for this rule so it can be triggered by other…