Bill Sheboy Expert

Hi @Kyle Bucher -- Welcome to the Atlassian Community! There are several ways I can think of to solve this use case...varying in degree of effort/complexity: * Add a delimiter after the priority score (e.g. a semicolon) and use the substringAfter() function to grab the rest of summary when updating:…

Hi @Don Doblados This technique is to use the text smart value and math smart value functions to split/parse the just released version to build the new one. Note for complicated names you may need to use a regular expression with match() and/or replace() functions. Please take a look at the format of your current version…

Hi! No need for another rule... One of the available smart values is {{createdIssue}} (or {{createdIssues}} when you have several). That value is immediately available once the issue is created, so you could branch on its key when you only need to access that one: {{createdIssue.key}}

Good ideas, @Remi Arts We use similar quick filters for those rather than swimlanes to raise visibility and improve focus. Thanks, Bill

Hi @Sam That is not possible yet; here is the suggestion to add that option, which you may watch/vote for to see progress: https://jira.atlassian.com/browse/JRACLOUD-74321 Best regards, Bill

Hi @Christina Leong -- Welcome to the Atlassian Community! For the #2 rule you note, please review and post an image of the audit log from an execution when the behavior occurs. This may provide some context to help the community offer ideas. Thanks! And just to clarify rule behavior... * In the rule you create a sub-task…

Hi @Juliano Granadeiro Working with your site admin, you could subscribe to a saved filter with a group. Then just edit the group membership as people join/leave. Please look here for information about how to do…

Hi @acertainsubset I do not believe that is possible with out-of-the-box Jira Server. You would need a marketplace addon to enhance JQL, or to use an automation rule to dynamically build the query based upon the current month, or export the issues to a spreadsheet for reporting. What problem are you trying to solve by…

Hi @[deleted] You note an automation rule is behaving/creating different outcomes for different people. Please consider posting an image of your rule and an example entry from the audit log when this symptom occurs. That may provide more context for the community to offer ideas. Thanks! Best regards, Bill

Hi @Sarah Baker Yes, and...to what Trudy suggests: the Story Points field is used for Company-Managed projects. For a Team-Managed project, please use the Story Point Estimate field. Best regards, Bill

Hi @Gian Israel Nampi Although not directly related to your observed rule symptom, there is definitely some interaction between that comment added trigger and user condition testing in the rule engine. Regardless... Two things to check: * Is this a project scope rule (stored in the project) or global scope? If it is in the…

Hi @[deleted] I found an open defect for this issue for the cloud version, but not for server: https://jira.atlassian.com/browse/JSWCLOUD-18121 My questions would be: If these fields were required prior to the split, how are they empty? Or, is splitting somehow clearing the fields? Best regards, Bill

Hi @Angel Osberg You cannot do that with out-of-the-box Jira, unless you convinced the teams to align their status values for consistency...which may not work for your teams. I can think of several possible work-arounds, each with varying costs/pros/cons: * Investigate marketplace add-ons which allow…

Hi Rosauro, I am not currently using any of those, and you may search for them here for your server edition: https://marketplace.atlassian.com/search?hosting=server&query=JQL In the comments from @Vikrant Yadav they are noting a solution that would use the ScriptRunner addon with the issueFunction feature. Best regards,…

Thanks, @Curt Holley for that explanation of how to compute the SAFe version of WSJF once a team has identified the supporting measures. For teams trying to understand WSJF better and the challenges/supporting ideas around its usage, I recommend reviewing the primary source on the topic: The Principles of Product…

Update from Atlassian support, as of 17 May 2021: Over the last several weeks, there have been intermittent latency issues with some REST API calls, and several customers are experiencing the symptom/error we observed. The relevant calls are: Create an IssuePOST rest/api/2/issueUpdate an…

Hi, @Estelle Bailly As the issues/improvements are worked out in the new view, there is a more complicated work-around you could try: automation for Jira. Let's say you had three defined sets of people you wanted mentioned in the description field. You could use an automation rule for each add the people as the automation…

Thanks for posting your rule, @Iain Short I agree with @wwalser about the built-in branch processing for that webhook trigger. If the error is misleading/confusing your team, you could instead: * use the generic webhook trigger (no issues), * create the version, * parse out the issue key list out of the data with string…

Thanks for explaining. If you believe this is a short-term need to help improve capacity balancing among team members, consider if you can do this with a manual/team-supported technique, such as a spreadsheet. However if you believe you will need this for the long-term, please investigate marketplace addons to support time…

Hi @Matt Henson I am not using that add-on, so I cannot answer your question. Have you asked the vendor what the possible values are so you may query them?

Please post back what you learn from support. Thanks!

Hi @Matt Henson Looking at the common warnings, I expect you could create queries for some of them but not all: https://confluence.atlassian.com/advancedroadmapscloud/common-warnings-998651244.html JQL is not a SQL, and some of these warnings would require comparing fields at different issue levels, parent and child and…

Yikes, and sorry to hear that. I hope support can find something for you. My site admin and I did some tests, and found that when deleted by a person, the audit log continued to show rules removed by a person. (I worried that like issues, deleted rules from cloud would vanish all traces.) As there is no other way to delete…

Hi @Jon Rosen -- Welcome to the Atlassian Community! I do not believe there is anything in out-of-the-box Jira to do this. There appear to be marketplace add-on for this, and I haven't used any I could recommend: https://marketplace.atlassian.com/ Best regards, Bill

Hi @Artem Fomin -- Welcome to the Atlassian Community! I have not seen rules disappear permanently/been deleted mysteriously before in our cloud instance. Some of our users have been confused by the label filtering of rules hiding things. And, I have seen the rule list get "stuck" so it didn't paint the list when…

Hi Davi, Given what you describe you may want to investigate marketplace addons for this type of reporting. The logged time hours are in Jira logs, and they are difficult to access as you request by status and by date/time. To do this manually in a spreadsheet, you would either need to use webhooks to push data or the REST…

Hi @lukec You may be able to do this by removing the prior values from the Watchers using changeLog or fieldChange. Please look at this help to see how those work: https://confluence.atlassian.com/automation/smart-values-993924860.html Best regards, Bill

Hi @soubirou I does not appear those fields are available from smart values...yet. They are available via the REST API: https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/#api/2/configuration/timetracking-getSharedTimeTrackingConfiguration So, I believe you could make a webrequest to the REST API, save the…

Hi @Jackie Lariviere -- Welcome to the Atlassian Community! You may do this with an Automation for Jira rule. It would be something like: * Trigger: issue transitions to QA * Action: send email (or send message to Slack) You may add additional conditional logic as needed. Please see here for some information to get you…

Hi @Vero Rivas How about Automation for Jira, removing teams' repetitive tasks (and reducing errors) to help them focus on more useful and unique delivery of value? Best regards, Bill