Bill Sheboy Expert

Hi @MJJALP For a question like this, context is important for the community to help. Please post the following:* what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule in a single image for continuity, * images of any relevant actions / conditions / branches, *…

There is an open suggestion to add secrets storage to support automation rules: https://jira.atlassian.com/browse/AUTO-1365 Until that is added, I do not believe there is a built-in, secure place for such information when using the Free license level. Perhaps check the Atlassian Marketplace to learn if one is available…

Hi @Lauren Maguire -- Welcome to the Atlassian Community! There is nothing built-in to do this, and the possible workarounds depend upon how often you need it and willingness to spend time / money... * need this one time* export the issues to a spreadsheet and perform the math there * need this often* have money to spend*…

Hi @Flavien Gache The keys for solving a scenario like this are: * get the distinct values for the child issues * use list iteration to build a dynamic JSON expression * use a single update with JSON to avoid timing / collision problems for multiple field updates For example, let's assume the child issues are subtasks, and…

Hi @André Siopa -- Welcome to the Atlassian Community! Jira boards are a view of issues based upon the board's filter. Did you ensure your created issue matches the filter so it can display on the board? Next, there are two additional criteria for displaying issues on the board: * For a Scrum board, the issues must be in…

Hi @nubdienub -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following:* an image of your complete automation rule in a single image for continuity, * images of any relevant actions / conditions / branches, * an image of the audit log details…

Hi @Khira Niemeier Rather than using an Advanced Branch to add the labels, I recommend using a list iterator over the parent values and add them with one single edit using a dynamic JSON expression for labels. This will be faster, less likely to fail if there is a single rule error, and not cause any rule timing problems…

Hi @Shikhar Pahadia Yes, and...to the questions from @Yatish Madhav How will this new comment structure impact iteration over comments, such as in automation rules? Specifically, will the comments remain ordered by the created date / time (perhaps with a parent ID added for context within the comment chain) or will the…

Hi @Christopher Thank you for this article showing examples with the new jsonStringToObject() function. I found that function helpful in scenarios such as accessing the Jira Product Discovery (JPD) date field attributes more easily. Please consider adding the new flatten function to the smart value documentation, either in…

My frequently used templates are ones I made: * remote retrospective templates with whiteboarding tools * in-person retrospective templates as printable docs * one-page, how-to guides for people new to RCAs, etc. * a large library of automation rules to copy / modify for team needs

What is the project type: JPD, software company-managed, software team-managed, etc.? Also from the screen images, it appears the export has a field named "Estimated" but the issue list has a longer name, based on the ellipsis ... at the end. Are there two fields with similar names?

Hi @Mariela de la Torre -- Welcome to the Atlassian Community! Is this for a Jira Product Discovery (JPD) project? What is the type of your "Estimated" field? Kind regards, Bill

Hi @David Weir -- Welcome to the Atlassian Community! When an automation rule updates an issue, such as assigning the Fix Version, that updates the database only. It does not update the in-memory data the rule has for the issue. This is done for both performance reasons and because the rule may need access to the data from…

I was describing enabling the time tracking features. Once those are enabled, the Log Time features allow using fields such as Original Estimate. https://support.atlassian.com/jira-software-cloud/docs/what-are-time-estimates-days-hours-minutes/ Please discuss this approach with your project admin and team before…

Hi @iatkinse -- Welcome to the Atlassian Community! Yes, that is possible using the automation date / time functions, and either conditional logic or a lookup table to map the values. However, I recommend trying something different as Story Points are normally used as a relative measure rather than as only a time-based…

Hi @Andrew MacDonald -- Welcome to the Atlassian Community! First thing, I do not work for Atlassian or any marketplace vendor; I am just another customer. With that out of the way... I suspect for a Free license level, there is no way to turn off that alert; perhaps disabling all outgoing emails for the site would do it.…

No worries, and I recommend using the feedback button to add your reporting suggestions and perhaps watching... The JPD roadmap https://atlassian-product-managers.atlassian.net/jira/discovery/share/views/a0af4caf-5f1b-42be-8c57-24d1080122bc?selectedIssue=JPR-5&issueViewLayout=sidebar&issueViewSection=overview The JPD…

Please pause to consider on which issue this rule is starting, then which smart values should be used, and the differences between "issue links" and issue parent / child relationships using the "parent" field. Based on the audit log, the rule triggered from CPD-500, and so this audit log write: Parent Issue Key should be…

Just to be clear, I am not an employee of Atlassian or a marketplace vendor; I'm just another customer. And I agree: there should be better built-in reporting / reuse of existing product features in the different areas.

Without seeing the full scenario, my answer would be: maybe ;^) List iteration can definitely be nested, such as with this made up example: {{#lookupIssues}}{{#components}}{{#if(equals(name.toLowerCase(), "squirrel"))}}found {{name}}; {{/}}{{/}}{{/}} Let's see one how well this resonates with your scenario... What if I…

From a rule maintenance perspective, using the JQL will be easier for others reading your rule to understand. From a performance perspective, the data is already loaded in the issuelinks smart value; using that approach saves a few seconds per rule execution over making another roundtrip to the database with the lookup.…

Just to confirm, what type of project is this for: company-managed or team-managed? If this is for a team-managed project, their issue types are unique for each project. That is, the internal ID for the issue type is different even when the names are the same. The saved ID values in the Create Issue actions will not work…

Sorry, I should have read my own post more clearly :^) This one works for both cases, putting the default value of 0 before the long-format of conditional expression. {{#=}} FLOOR ( 0{{#if(varTotalCount.asNumber.gt(0))}}{{varDoneCount}}/{{varTotalCount}} * 100{{/}} ){{/}} More information... My earlier assumption was…

Hi @Dan Driscoll No, that is not one of the supported views: https://www.atlassian.com/software/jira/product-discovery/guides/views/overview#what-is-list-view You could check the Atlassian Marketplace and try one of the report apps / dashboard gadgets to learn if they can report what you need. There are several that…

Hi @Chris Smith -- Welcome to the Atlassian Community! Adding to the suggestion from @Vishal Biyani on trying lookup tables, please see this information: * https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-lookup-table *…

Hi @Samuel Imrich -- Welcome to the Atlassian Community! The likely cause of that symptom is timing (i.e., a racetrack condition) where the Project Created trigger fires before the project configuration (including the issue types) is fully available...leading to the errors you observe. For workarounds, something needs to…

Hi @Jan Rosar Please note well: parent / child data sum scenarios (e.g., to sum the child Story Points to the Epic Parent) span many possible cases. This is one of the reason there are marketplace apps to perform this type of field rollup / sync. Some of the cases can be combined into rules with one trigger and conditional…

Hi @Deepak -- Welcome to the Atlassian Community! With the Create Variable action, values may be stored as text and referenced later in the rule as a smart value: * https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-variable *…

Hi, @Amanda Barber I just checked the feed and at least one entry present earlier (between 10:20 - 11 am PT) is now gone, and the ones I expected to be present are still absent. This happens from time to time although I wanted to raise visibility in case others are seeing it after the updates. Thanks!

Awesome; I am glad to learn it is working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!