Bill Sheboy Expert

Have you found a specific Jira issue which you see has a value for Due Date? Does that Jira issue display on the board, regardless of whether or not it shows the field? If the card does not display, have you checked if there is another filter preventing display, such as the Kanban board sub-filter? You may find that filter…

In my experience, adding a business critical item after the sprint starts is an exception and not a normal practice. For example, some teams have production support responsibilities and so may work on an urgent item after the sprint starts. Fortunately this is visible with the Sprint Report. The team can review this report…

Hi Community! First thing, I am not an employee of Atlassian or any marketplace vendor. With that disclaimer out of the way... I fully support people helping to answer questions from other community members...in most cases. However this "packaging model change" is leading to specific licensing and billing questions. I…

If you scroll down in the issue view for ES-131, you will find the Activity section, with a History tab. Please select that, and find where the Story Point field was set after the rule was enabled. If you are not setting the Story Point field, a rule triggered on changes to that field will never run, and that may explain…

If your Fix Version will ever have more than one entry, using conditions will not work as expected as it will return a list of dates. In that case you may either add smart value, list filtering, or use the max function on the releaseDate in the list of versions.

Thanks, @Kelly Arrey Atlassian removed public access from that old Code Barrel backlog...which is too bad as there were a lot of good tips / work-arounds in there. It is unclear if all of the items got cloned over into the new backlogs for AUTO and JIRAAUTOSERVER, so thanks for the new one! Kind regards, Bill

Hi @Kelton Stewart -- Welcome to the Atlassian Community! I do not believe there is anything out of the box to do that for a separate custom field AND to exclude the current assignee. If you have a fixed number of people, I could imagine more elaborate work-arounds (which I have not tried) to implement random or…

Hi @Donna Benton Adding to Curt's answer... After the trigger, you could add a condition on issue type, and only proceed if it is a Story. Kind regards, Bill

Gotcha; for that filtering on the subtopics, that could be added to the JQL for a second Lookup Issues inside of the branching.

Hi @Michelle Rohan First thing, I do not work for Atlassian or a marketplace vendor. With that disclaimer out of the way... I believe you can do that with a rule, setting that field based on the resolved date, using the date/time format() function to convert to a value that will match your single-select field list. To have…

Sorry, I am out of ideas to try. Unless Trudy has more, I recommend working with your site admin to submit a support ticket to Atlassian for this one. You appear to be on a Standard license and so the admin can do that here: https://support.atlassian.com/contact/#/ When you hear back from them, please post what you learn…

Hi @Florisa Stephany de Souza Campos Do you mean the Automation for Jira rules? If so, yes that is possible with an addon. Please check with your Jira admin and look here to learn more information: https://confluence.atlassian.com/automation/jira-automation-data-center-and-server-993924595.html Kind regards, Bill

Hi @Bikram Agarwal -- Welcome to the Atlassian Community! You could try using the Send Web Request action to call the GitHub REST API function to create the PR. For more information about calling a REST API function from a rule, please see this how-to…

Hi @Simon Marks -- Welcome to the Atlassian Community! Have you seen this article about the changes to the epic panel now using the Status Category of the epic's Status (and no longer the sunsetting field Epic Status):…

Hi @philipf Have you checked if there are multiple fields named Due Date, such as where someone added a custom field with the same name? If so, the wrong one is displaying. Kind regards, Bill

Hi @Mark Berman Have you tried using the Manage Watchers action? Kind regards, Bill

Hi @Mykhailo Pavliuk Do you always have issues assigned to the next, unreleased version at that 5 day point? The answer will impact how you solve this. Yes, the team always has issues assigned... * Try using a scheduled trigger, with no JQL * Then use the Lookup Issues action, with JQL checking for…

Hi @Suganthan.Subramanian -- Welcome to the Atlassian Community! What do you mean by an "uncommitted or stretch goal"? When teams use Scrum, they may create a Sprint Goal, which is a single objective to achieve for the sprint. This provides alignment and focus for the team members and product owner. And, it is supported by…

Thanks for that information, and... If your "release end date" is in a swim lane name / description, isn't that likely to need changing every time there is a new release? Have you instead considered using the Releases feature of your Jira project, and assigning issues to a Fix Version? That might eliminate most of the…

I am still unclear what problem this is solving, and I suspect this will be a brittle solution to implement in an automation rule...primarily due to the difficulty to maintain it. Regardless, I continue with my earlier recommendation: * starting with A2 and A2, compute their conditional results and store them created…

Starting with your use of a lookup table, please see the information I provided as you do not appear to be using them correctly. The way they work is: * create a lookup table * retrieve a value from the table using the get() function, passing your key value as a parameter from a smart value or literal text value, to return…

Thanks for that information. Please try changing your JQL for the second lookup issues call to use the account ID value from the branch variable, like this: project = "IP" AND IssueType="Risk" AND "Next Review Date"<=1w AND "Next Review Date">= now() and resolution = "Unresolved" and assignee= {{distinctAssignee.accountId}}

Hi @Simon Galiazzo -- Welcome to the Atlassian Community! Have you considered using Clone Issue and clearing the fields you do not need? That will make copying the attachment easier. Back to your original question... To access that other issue as a source for copying to the new issues, try using JQL to find it and the…

Hi @mohammad lavasani -- Welcome to the Atlassian Community! Would you please clarify the problem you are trying to solve? It seem that you want: When an issue is created, copy a custom field from another issue, using an Automation for Jira rule. If you have started a rule, please post images of the rule, an image of the…

If you break the rule down into pieces, as you have already described, the rule is not too difficult. The only piece you have not yet accounted for is using the Re-fetch Issue action in some key places. * trigger: issue created * action: re-fetch issue (to force a data reload before proceeding) * branch: on JQL using the…

Please also show the history for a specific issue (e.g., a story) where the story point estimate changed after the rule was enabled. Also, you are using Time estimation, and not Story point estimation. How will that work for your team as the field will not be shown on the view, by default?

Hi @Coiram You could try splitting on the newline, converting into a list, and grabbing the first returned value: {{issue.comments.last.body.split("\n").first}} Kind regards, Bill

Hi @Donna Benton Have you tried to set the Due Date field using the option Copy from Trigger Issue when you create them? You can find that under the ... options to the right of the field: * select copy * change to copy from trigger issue Kind regards, Bill

Hi @James Phan and @Trudy P Claspill That is curious...I would have expected the initiator to either be the Automation for Jira user or the person who created the PR. I did find this defect indicating if a user does not have an email address in their public profile for Github matching their Jira profile, no match is…

I am glad to learn that is working with two rules, and...I just learned something new... Commenting on issues does not fire the generic Issue Updated event (and trigger), but it does apparently get picked up if a webhook is used (although I have not tried that). I found a few open suggestions in the public backlog for…