Bill Sheboy Expert

Hi @Delivery BU Resource Requests -- Welcome to the Atlassian Community! You do not need the extra curly brackets when using a smart value as a parameter to a function. Please try: {{issue.created.plusBusinessDays(issue.customfield_10050)}} Best regards, Bill

Hi @SAY -- Welcome to the Atlassian Community! You could use an automation for Jira (A4J) rule, triggered on the incoming webhook, and then create the issue. Please look here for information about automation rules: * https://www.atlassian.com/software/jira/guides/expand-jira/automation *…

Hi @Sundaresen Rungasamy How about adding a quick filter to find the issues with links of that type for the board? issueLinkType IN ("blocks", "is blocked by") Best regards, Bill

Hi @Manoj Khaire Adding on to the other suggestions that this feature is not available with out-of-the-box Jira... How often do you need to perform this check? If you need it just once, consider exporting the information to a spreadsheet and perform the check there. If you instead need it often, consider getting a…

Hmmm...maybe? With the smart value (field) updates, it isn't always clear what is needed. How about writing the smart value ... {{customfield_11701.value}} to the log in one action, and confirm it contains what you expect for the value as you try JSON for the edit in the other action? That will help isolate what is…

Donna, you could also try "what's in it for you" with product owners: when a team limits WIP and distractions, they have better focus, get stuff done faster/with higher quality, and are able to give their PO more accurate forecasting on value delivery. __Bill

Hi @Rodrigo Xavier According to this suggestion, that appears to be difficult currently as you would need the user's Slack ID in the message: https://jira.atlassian.com/browse/JRACLOUD-74092 The noted work-around is to store the Slack ID with the Jira user as entity properties, and then use that value. Best regards, Bill

Peter, please try this one to just set the ID field and see if that helps. Watch out for the quotation marks changing to curly/slanted type as the JSON won't like those. { "fields": { "customfield_12000": { "id": "{{customfield_11701.id}}" } } }

Hi @Shawn LoPresto Yes, and...to what Trudy suggests... At what scope/scale do the "Joint Feasibility Analysis and Join Application Design" occur: idea, epic, story, task, etc.? If they occur only at the epic level, leading to the subsequent work break-down for the other issue types, why would those fields be needed on the…

Hi @Donna Malgieri Agreeing with Trudy's suggestion, and perhaps consider this as a topic in the next retrospective to decide how the team can improve to prevent it in the future. Best regards, Bill

One more thing to check: is this a project-scope automation rule, or a global-scope rule? If this a project-scope one, I found an open defect for this problem/symptom: https://codebarrel.atlassian.net/browse/AUT-1495 If this is global-scope, I believe that should work, and so please consider asking your site admin to…

Hi @Peter Yoon Adding on to what Trudy suggests, if you are unsure what the smart value of your field is, please use the technique described here to find it: https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/ Then try this for a single-select field, replacing your custom field numbers…

Can do! Here is what I did: * Selected the clone action * Selected the fields I wanted * Selected the reporter field, selecting the ... at the right of the field and the option to copy from current issue

Thanks for explaining, @Jonathan Cunliffe Regarding the "multi-project board", what I was suggesting was something like the following for the shared board: * Rather than use an issue type of Dependency, link the issues which are dependent. Perhaps creating a link type of "dependency", or using the existing "blocks" and "is…

Hi @Bruce Robinson When I tried that in an automation rule, copying the Reporter from the trigger issue, it worked for me. I have noted posts for that error message/symptom when either the target field was not on showing the page view configuration or a duplicate custom field of the same name had been created. Would you…

Greetings community! Reviewing some of these "new" plays, I wonder at how many of them seem like rebrandings of existing ideas from Liberating Structures, Management 3.0, Innovation Games, and the works of Jean Tabaka, Alistair Cockburn, R. Brian Stanfield, etc., yet without referencing those sources. Perhaps I am missing…

Greetings! Decision making has "who" and "how" components, and I recommend looking into Delegation Poker to support the "who" for team decision making. This method supports the idea of balancing autonomy with maturity level, and that teams progress over time to gain autonomy with maturity. Check out this book for more…

The teams I support regularly do this during retrospectives, with a "deep cleaning" during our annual retro. We often use a tool like Trello to show a skeleton of our workflow and rituals, and brainstorm/discuss with 1-2-4-All on the areas, and define our next improvement experiments to see what we can learn next.

Hi @Thiemo Hiecke -- Welcome to the Atlassian Community! I do not believe that is possible yet, based upon this suggestion: https://jira.atlassian.com/browse/JRACLOUD-76835 One work-around would be to export all rules to JSON, and then search the results for what you need to know. We did that to find use of certain custom…

Hi @gemma.pickman -- Welcome to the Atlassian Community! I do not understand how the diary format you describe would answer those questions. And there may not be anything built-in for out-of-the-box Jira to do that across all the projects and people (Jira users). It seems like you are describing a people…

Hi @Rafael Francisco Garabato Bonino Either one of your ideas should be possible with text functions and regular expressions...And I am a bit unclear on your flow of events. Perhaps mapping out that will help you create the rule. For example some questions to help guide that: * Are you manually creating the versions before…

Hi @Kathy Barton For an automation-related question like this, please consider posting an image of your rule and the audit log from an execution of it. That will provide context for the community to offer you suggestions. Thanks! Best regards, Bill

Hi @Jonathan Cunliffe Yes, and... to what Jack notes about the global/multi-project execution limits, I wonder how you are using that automation rule. Your rule describes linked issues in multiple projects, and when one issue of Dependency type transitions, all of linked issues do also. That seems to indicate those issues…

The documentation doesn't say anything about needing specific permissions except at the global level, so perhaps ask one of the project admins to try it: https://confluence.atlassian.com/automation/view-performance-insights-1013851985.html

Hi @Krithica G Are you using the Lite (free) or Pro (paid) version of automation for Jira on server? For the Cloud version, project admins can see the performance measures for their respective projects; it is under the ... menu at the top-right of the automation rule list page. Best regards, Bill

Hi @Johan Potums -- Welcome to the Atlassian Community! Yes, and... to what Derek suggests, when you need to do this type of query often and for different issues, you could build an automation rule: * create a rule with a manual trigger * calls the REST API as Derek notes * search the response for the triggering issue key…

Hi @Abdullah Bakhach For a built-in way to do this, you could try the Jira Issues Calendar gadget on dashboards, and display your versions (releases). If you specifically need something more like a line or bar chart of release counts, you may need a marketplace addon or to export data to produce that visual in another…

Hi @[deleted] -- Welcome to the Atlassian Community! How often do you need to do this, and do you have funds to purchase marketplace addons? * When you need this once: consider exporting your issues to a spreadsheet and perform the comparison there * When you need this often and have funds for addons: consider marketplace…

Thanks for explaining, Lee. For teams to see each others' work you have a couple of options I can think of: * Have them look at the other team's board, when needed * Create a board to show the shared work by making a filter the shared work, and then creating a Kanban board (stored in a company-managed project) specifically…

Hi @Derek Fields _RightStar_ Thanks for the write-up! Have you noticed any timing issues between your steps 3 and 4, where the just completed issue gets picked up by the branch? I wondered due the asynch processing of branches with more than one issue. If so, might a re-fetch after the transition and prior to the branch…