Bill Sheboy Expert

Hi @Dean Harvey Here are a couple of suggestions related to adding that capability, which you may watch/vote for: https://jira.atlassian.com/browse/JRASERVER-61889 https://jira.atlassian.com/browse/JRASERVER-62458 Best regards, Bill

Hi @Francisco -- Welcome to the Atlassian Community! You cannot do that with out of the box Jira queries using JQL. You may want to investigate the marketplace for add-ons to scripting to help: https://marketplace.atlassian.com/ Best regards, Bill

Hi @Sou, Eric When a product owner gives me a challenge like you describe, I find it helpful to discuss symptoms with the team before discussing solutions to...well...the symptom rather than the root cause. A larger backlog may indicate: * Nostalgia or stubborness ("one day, we will fix that defect from 5 years ago that…

Hi @Chase Wilson Interesting, and... Which versions of Jira Cloud will support Jira Work Management out-of-the-box, or will this be an add-on capability (with additional costs)? It was unclear to me from this post or the linked one on FAQs. Thanks, and best regards, Bill

Hi @Ivan You probably cannot do that with out-of-the-box Jira. You could use the REST API to get the sprint information as JSON, and convert it as needed. Here is the documentation on a couple of calls that would support that. https://docs.atlassian.com/jira-software/REST/7.3.1/#agile/1.0/sprint-getSprint…

Hi @Artjoms Jakovenko -- Welcome to the Atlassian Community! Automation rules are either enabled or disabled, not by a specific issue. If you have specific criteria in the issue you want to decide when a rule runs, that criteria may be used by triggers and conditions to limit rule execution. Best regards, Bill

Hi @Miko Stefanov Does the smart value {{pullRequest.destinationBranch}} have the information you need to perform the comparison? https://support.atlassian.com/jira-software-cloud/docs/smart-values-development/ Best regards, Bill

Hi @Nawaaz SOHAWON Automation doesn't load all the issues in the tree (issue to parent to links...) into the scope at run time. Instead, I believe that you will first need to get at the parent issue, perhaps using a Branch statement, and then store the value in a Create Variable. Then you could use that variable's smart…

Hi @Mateusz Przybyłek Thanks for that additional information... Now the question is how do you decide which sprint to put an issue into when multiple ones are running? The automation rule can only select correctly when it has the same information/choice-making you use. For example, if you are running parallel sprints for…

Sorry, I am unclear how you can do what you suggest if the value you use for Epic Name is not unique. You would need something to match on. Somehow your external app has information about epics (perhaps as the original source to create them?) and you may want to consider also storing the Key to make look-ups with JQL match…

I am glad that helped! Automation documentation has some info gaps, and so it can help to experiment and see what is possible. And, watch these posts for ideas and updates: * https://community.atlassian.com/t5/Automation-articles/Jira-Automation-all-the-resources-you-need-in-one-page/ba-p/1388465 *…

I made a test rule for this use case, and when editing the fixVersion of the issues in the created sprint, I just entered {{sprint.name}} because my version names exactly matched the sprint names. That worked as I did not assign them to the latest unreleased version, avoiding the confusion you note for parallel sprints. If…

Hi @Erik Beltran JQL is used to filter issues, so those are always the focus with that feature. There isn't a query for projects. To see a list of all projects to which you have access, from the top navigation please select Projects > View All Projects. If you wanted to get all the project data to build a report, you may…

Thanks for that information, Arthur. I was suggesting to wait until the sprint starts to create the version, rather than doing so when the sprint is created. That prevents version errors (sprint created and then deleted without starting), and ensures the issues are assigned to the version for their respective sprint. Even…

Hi @Arthur Bershadskiy -- Welcome to the Atlassian Community! Would you please share your naming convention for your versions and sprints? Those may provide ideas for the community to give suggestions. Thanks! Also, have you considered waiting for a sprint to start to create the new version? That could ensure a pairing of…

Hi @Mykola Kharchuk I look forward to seeing what you discover on this concept for SaaSJet. You may want to try a browser search on other mapping and board tools for comps, as I recall seeing "history" views in other tools (a while ago) with a time-frame slider to show the changes based upon the position of the slider, and…

Hi @Richard Freisberg When I pasted your smart value string into a plain text editor, I noticed that the second quotation mark is a slanted (curly) one: -------------------------------------------------| reporter: {{issue.description.match(".*(parker).*”)}} Please try replacing that second quotation mark and see what…

Hi @Renata One way to achieve what you ask is with automation rules, triggered on the comment and checking the issue type before posting the message to Slack. Please see this information to get you started: https://confluence.atlassian.com/automation/automation-for-jira-server-7-2-documentation-993924595.html…

Hi @Todd Adel What are you seeing when you try that filter for the board? And, do you have issues without epics? If so, you may want to also check for empty epic link, such as: project = X AND labels = xyz AND ("Epic Link" != X-123 OR "Epic Link" IS EMPTY) ORDER BY Rank ASC Best regards, Bill

Hi @Gene Schulze One work-around for no sprint-level custom fields is entity properties. You may manage them with automation rules, the REST API, or by using an add-on from the marketplace. Please look here to learn more about this feature: https://developer.atlassian.com/cloud/jira/platform/jira-entity-properties/ Best…

I am glad to hear that worked for you. When you use the Scheduled trigger with JQL that helps when you need to process each item one-by-one, such as for editing. Lookup Issues is when you need the set for non-edit stuff, like counting or reporting.

Hi @Chris Buzon How about driving this from the issues as they transition using Automation for Jira? For example, when an issue transitions to "done", and it has a fixVersion, use a couple of LookupIssues action with JQL for (1) issues in the same version, and (2) issues not-completed in the same version. You may then…

Hi @Chip Plowman I tried this and these worked, once I confirmed that the triggering issue was an Epic: {{issue.Start Date.minusDays(7)}} {{triggerIssue.Start Date.minusDays(7)}} Best regards, Bill

Hi @Raymond Jenks -- Welcome to the Atlassian Community! Are you using an automation rule to do this? If so, you could try something like this: * Trigger: scheduled once per day (perhaps at a specifc time using a CRON expression) * Action: Lookup Issues with JQL to find issues in your status * Action: send a message to…

Hi @Sebastian L_ For something like this, please post an image of your rule to provide some context; that will help the community suggest ideas to you. Have you tried logging the values to the audit log to see what they contain within the rule? If your fieldChange field is already a number, you should not need to convert…

Hi @Franck LEVESQUE -- Welcome to the Atlassian Community! For an issue (like a story, task, or bug) which has a parent epic, the Epic Link field is the key to that parent epic. What are you seeing in the field? Best regards, Bill

Thanks for clarifying, Brian. Yup, the version of a "CFD" in Jira is missing many assumptions and features of a CFD, including measures at a point in time (and not continuous). Yet another reason we need a generic built-in Jira gadget to "show me any field or log value over time with basic statistic measures". Until then,…

Hi @Trevan Householder_Isos-Tech-Consulting_ Excellent use case! It appears there are several looping-related ideas in the backlog, so please take a look here. Unfortunately customers cannot watch these as they are in the Code Barrel backlog.…

Hi @[deleted] Yup, at this time those fields and functions are not available within Lookup Issues: * https://codebarrel.atlassian.net/browse/AUT-1996 * https://jira.atlassian.com/browse/JRACLOUD-75018 One work-around for your use case is to use a custom field and scheduled rule to compute the age, and then subscribe to a…

Hi @Mateusz Przybyłek Please post an image of your rule to provide some context for the community to suggest ideas. The criteria you use to trigger creating the defect (bug) may provide what you need to find the sprint. Seeing the rule and its conditions will help confirm this. Thanks, and best regards, Bill