Bill Sheboy Expert

Hi! Yup, and perhaps they were implying "minimum" for that. (Again, an opinion. :^) For other references specifically on MVP/MVI, please check in books from: Ron Jeffries, Jeff Patton, Marty Cagan, Mike Cohn, Alistair Cockburn, Mary and Tom Poppendieck. Whatever you discover, you may find it helpful to gather people on…

Yup, that sounds correct. Apparently the assumption is people using CMP with Kanban are using pull-based, release-driven processing...and so that sub-filter makes sense to keep the board clean. Some of our Kanban teams want released versions to display longer (e.g. until the next Queue Replenishment/Refinement) and they…

Thanks for explaining, Fred. With the built-in burn charts and only one sprint spanning the teams, I do not see how you can do that. You could investigate marketplace addon gadgets which support filters for burn charts, as that could help. Another way to solve this is with a chat: * Consider a conversation with the new…

Yup, that makes sense for the same reason: the replace function is taking two string parameters. I am glad to hear that is working. Please consider marking this question as "answered" to help others in the community searching for solutions find them faster. Thanks!

Hi @Samuel Thomsen Given TMP create all their own values for status, you could try the status ID value for your query when you need to narrow the results for a project. Best regards, Bill

Thanks, and that may mean some typing-issues are happening. Please try: {{issue.A.value.replace("Four","4")}}

Hi @Breeze -- Welcome to the Atlassian Community! I expect that even "references" are going to be "opinions" on this topic. :^) As you note using the scrum framework, please consider looking at The Scrum Guide for this idea: https://scrumguides.org/scrum-guide.html#increment Best regards, Bill

Hi @Alasdair McKie How are you representing Milestones within Jira? With issues, addon application, something else? What do you mean by having the Sprints "drive the dates" of Milestones? For example, when each sprint is created, is sets a Milestone x-weeks in the future, or something like that. Best regards, Bill

Hi @Oriyet Tibi -- Welcome to the Atlassian Community! I am curious: what problem are you trying to solve by doing this? When creating a plan, people often want to see relative progress: what work is not started, in progress, and completed. Removing the completed items would seem to reduce the value of even creating a…

Hi @Gautam Poddar -- Welcome to the Atlassian Community! When you note "...none of the following expression syntax working for me...", what are you observing happening? What do you see in the audit log? Have you tried to split this expression up incrementally and write to the audit log to see what is happening? For…

Hi @binay_yadav You may want to consider having a conversation with the team to better understand why issues are added to a sprint without sizing (story points). For example: * How often does the team refine work prior to sprint planning? Perhaps that activity is missing, and so the team feels rushed during planning,…

Hi @MA Yes, and...to what @Jack Brickey notes: here are the suggestions to add that feature for category scoping: * https://codebarrel.atlassian.net/browse/AUT-805 * https://jira.atlassian.com/browse/JRACLOUD-76420 For work-arounds... * What you describe with a category condition test using all projects scope seems like a…

Hi @Margaret Medon Full disclosure that I am not using the XRay app, so others in the community may have a better answer. When you add test steps the issued updated trigger is firing, so you should be able to detect that change: * If you can select that specific field in the trigger, that is probably a good approach * If…

I am glad to learn that helped you, and I hope that you have a great vacation! __Bill

Thanks for clarifying, Scott. The scheduled-trigger rule looks like it could help. Something else to consider: why are stakeholders not verifying those issues when they are ready? Are they too busy, do they find it unnecessary, have they moved on to other concerns, etc.? Having some quick chats with them may lead the team…

Hi @Nice AtlassianLicenses With built-in JQL, probably the closest you can do to solve this is create a JQL query, sorted by summary and then created date, then look at the last one in the list. project = myProject AND summary ~ "text I am looking for" ORDER BY Summary ASC, Created ASC Best regards, Bill

Hi @Holly Schomann How about this one, adjusting your timeframe to check Resolved: project IN (GS, SC, PUB, "CF", ECOM, STU, TCS) AND sprint IN closedSprints() AND resolved >= -14d ORDER BY project ASC, key ASC Best regards, Bill

Thank you for explaining further. Possible work-arounds are to: * find ways to identify sub-sets of the results, and use multiple Lookup Issues JQL calls to pull the results in chunks * use the REST API to get the count of issues, sent the report, and conditionally add a statement and filter to the email: "There are more…

Thank you for explaining, and you would need an addon to do this with JQL. If you only need this once/a few times, you could also export the data and perform the check manually in a spreadsheet. As an another work-around: you note that Actual Start Date is filled in automatically, perhaps with an automation rule. When that…

Hi @Sean Lin -- Welcome to the Atlassian Community! Another thing to check is the "Kanban board sub-filter" to see if it is excluding anything. You may find this at the bottom of the general settings page for the board settings. Best regards, Bill

Hi @Alaa Alsharif Agreeing with what @Jack Brickey notes, and... What problem are you trying to solve by showing all of the sprints on one burndown chart? Knowing that may give the community more ideas to suggest. Thanks! Best regards, Bill

Hi @Julia Foden Although I wish lookup issues supported more fields, that may not be added due to performance and other issues. A work-around for your use case with lookup issues is to use JQL to order and grab the relevant issue's key: * action: lookup issues on JQL for the sub-tasks which orders by the custom field,…

Hi @Alghaida Aljuraisy -- Welcome to the Atlassian Community! As noted by @Gaurav you can solve this with a global/multi-project scope automation rule, and... Please check with your site admin on your license level, as each level has different limits on how many global/multi-project rule executions are permitted. For more…

Hi @Fred Safian -- Welcome to the Atlassian Community! The reports are associated to the filter driving a board. Some reports have additional filtering and I do not believe those reports do. You note helping multiple teams. If these are teams using scrum, I would expect they would each have sprints, and so would use…

Hi @Jaqueline Cuatepitzi Bastida With out-of-the-box Jira's JQL, you cannot write a query to compare two fields; JQL is not a SQL. There are marketplace addons for purchase which may add this ability. And, when you note "project" do you mean Jira projects? If so, then this query would not be possible as Jira's JQL looks at…

Hi @Jose Ariel Laureano Ramirez Running a JQL statement from the user interface will not show the count when it is above the limit. However if you call the REST API search method for your JQL the "total" field will show the count. Based upon your other recent questions/posts, I wonder if this is this for an automation…

Hi @Scott Howard Forbes -- Welcome to the Atlassian Community! The two things you note seem to be contradictory: * trigger the rule when it is transitioned, AND * you want a period of inactivity before taking an action As @Brittany Wispell notes, this may be better supported with a scheduled trigger, perhaps on JQL…

Hi @Jose Ariel Laureano Ramirez Short answer: no. Even though Lookup Issues returns a limited set of fields from issues, automation rules are limited to the number of issues returned/impacted...most likely for performance reasons and accuracy (data could become out of date by the time the rule finished otherwise). What…

Hi @Jose Ariel Laureano Ramirez -- Welcome to the Atlassian Community! Yes, I believe that is correct. To get the name of the status, please use {{status.name}} with Lookup Issues. Providing the id number allows you to compare status values which may have the same name and different values across projects. Best regards,…

Hi @Andre Menezes That will probably be {{issue.Target Population}} as it is inside of the branch, and so will use the parent's value. You may need to use the custom field ID instead if the name doesn't work. If neither works, please use the information in this how-to article to learn the smart value for your…