Bill Sheboy Expert

Yup, that sounds correct. For use cases like this, I found another approach that can sometimes work: You appear to be using an advanced branch, based on a web request call's response. Instead eliminate the branch and use a list iterator on the response and extract all the needed values into a single created variable in one…

Hi @Ricardo Serrudo I do not believe that is possible with out-of-the-box Jira features. Here is an open suggestion from 2012 to add that capability: https://jira.atlassian.com/browse/JRACLOUD-28225 There's an update on the suggestion from Atlassian staff from March 2022 that it is on the roadmap now, so perhaps watch/vote…

Hi @pierre Is there only one person on the scrum team? If not, what problem are you trying to solve by measuring this for individuals rather than for the entire team? Measuring by individuals for a scrum team can create unintended consequences, such as reduced trust, collaboration, respect, and delivery of the most…

Hi @Sharmila Chinnasamy -- Welcome to the Atlassian Community! What do you mean by "Scrum capacity planning"? For example is it one of these: * Using the team's historical velocity, plan how much the team might finish in future sprints * Using the team's people availability (e.g. days and hours available for a future…

Hi @Team Logistics Sigma You appear to be using a team-managed project. To add the fields for that one: * select an issue on the board or backlog * at the bottom of the issue view, you will see a gear icon and Configure fields * select Configure fields, and now you can add your labels to the view…

Hi @Nathan Broom -- Welcome to the Atlassian Community! I am assuming you are trying this in an automation for Jira (A4J) rule...and so your scoping observation is correct. Branches in automation rules which have one-and-only-one value (e.g. Branch on Parent, Branch on Current Issue, etc.) get run in-line, and so any…

Hi @johnson Yes, and...to Trudy's answer: there is an open suggestion to make that display timeframe configurable. You may watch / vote for it to see progress. https://jira.atlassian.com/browse/JSWCLOUD-22312 Kind regards, Bill

We would use such a board as a card-based roadmap view of when idea will deliver to production. This seems better than the Gantt-like view in Jira roadmaps, which is more relevant in conversations for dependency and capacity issues.

Hi @Ando - ibs000 What have you tried thus far for your rule? If you are just getting started, please review this documentation and examples: * https://www.atlassian.com/software/jira/guides/expand-jira/automation * https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/ *…

Hi @Marcus Hicks -- Welcome to the Atlassian Community! What problem are the four people trying to solve by seeing all of those issues? Perhaps rather than showing them just a list, some specific questions could be answered/summarized using the built-in dashboard features of Jira. Kind regards, Bill

Hi @Hagay Short answer: This may not be possible using {{index}} that way, and there is at least one work-around Longer answer: Smart value, list filtering appears to only access the issue fields; {{index}} is an attribute of the list, not of any of the issues. And so it cannot be used in the filtering or apparently with…

That sounds correct: the parent branch typically works for epic/children. There is a separate one for linked issues. But your case of going up to the "parent" issue using links instead you may need a JQL branch.

No worries, and I am glad you got it to work! Short explanation on the bulk-handling for Server/Data Center Jira...When that option is enabled, you can treat the results (from the trigger or branch) as a set, and the smart value {{issues}} (note the plural) is available. This helps in cases such as sending one email or…

Thanks for the honest views on this feature, @Tanguy Crusson What you describe for the new type of date field would help; perhaps the missing part is what I described about how filters work with views: * Given I am using a board view with date-based columns, * When filtering the board on the column field (which is not…

I do the same, Trudy..."I wonder if I could create an automation rule for that..." :^)

Hi @Nikhil Nanjangud -- Welcome to the Atlassian Community! As you note you already have a separate query for the created issues, you may add this to your update query: AND created <= "some date" That would restrict to only those issues changed after your date and created before that point in time. Kind regards, Bill

Hi @Porush Verma To see that time in status you may use the built-in Control Chart as described here: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/ To see the time for just one status, change the options to only select that one status and you will see both the specifics for…

Hi @Gisela Lassahn For the Server/Data Center version of automation, I recall there is a "bulk handling" setting possible for branches (and scheduled triggers). Is that setting enabled or disabled for your branch? It seems like you would want it disabled based on the way your rule is described. Kind regards, Bill

Hi @Dąbrowski Damian It is difficult to see what is happening in your rule as it is split across 2 images. Please consider capturing the rule image using a browser extension to scroll/capture the rule in 1 image. Until we see that... When using the Issue Created trigger, or when editing the issue within the rule, consider…

Hi @Swati Mathapati That appears to be a third-party extension to automation from the marketplace. Have you checked with the vendor to learn what they suggest? Kind regards, Bill

Hi @Gil Blau What is not happening as you expect? What do you observe when you look at the details of the audit log after the rule has processed? Kind regards, Bill

Hi @Rich Evers The days in column feature uses the issue history data, and you may learn the specifics about what is displayed here: https://support.atlassian.com/jira-software-cloud/docs/customize-cards/#Using-Days-in-column Kind regards, Bill

Looking at the references Trudy provided, there is more flexibility for the release notes with Server/Data Center version. Please take a look a the tutorial for information on formatting the notes produced. If you need something more, you may want to investigate addons from the Atlassian Marketplace.

Yes, you have explained it well: save the assignee you want to return to (when in the development status), and use that later to re-assign, as needed. For example to do this as you describe, first work with your admin to create the "Original Dev" custom field as a single, user field. Then in your rule... * trigger:…

Hi @Gabrielė Vlasova I reproduced the same symptoms using {{issue.issueLinks}} and the lower level smart values {{issue.issueLinks.inwardIssue}} and {{issue.issueLinks.outwardIssue}} So this appears to be a defect, and I recommend working with your site admin to submit it to Atlassian. I did not find any similar defects in…

Hi @ABDULRAHMAN You appear to be using a team-managed project. If that is correct... The project admin needs to enable the Releases feature for the project: * from that left pane, select Project Settings * then select Features * then enable Releases Kind regards, Bill

Hi @Kevin Phang Without seeing your rule, I wonder if this can even work: rules have a processing limit of 100 items for triggers, branches, lookup issues, etc. Unless your rule is constructed to repeatedly run in chunks (e.g. with a scheduled trigger and JQL condition), I wonder how this can work. Are you observing a rule…

Hi @Eric Hammes You seem to have listed most of the options people will probably suggest. I have a question: are your Issues (story, task, bug) individually releasable to production? You note a want to "avoid communicating every incremental step along the way", so perhaps they are not releasable. If they are releasable,…

Thanks for your fast response! My answer for granularity: yes and no ;^) * I can see use cases based on context (e.g. what is relevant to highlight for this view of the portfolio...with specific filtering and sorting)... * versus what you describe: aligned understanding of what things like "readiness" or "urgent" mean…

Hi, Phil. Sorry for the delay in responding as I was out-of-office. I just tried this for active sprints in a Company-managed project and it maintained the order from sprint start, regardless of the dates associated to the sprints. I suggest working with your site admin to ping the support team for this if you are seeing…