Bill Sheboy Expert

That smart value expression looks well-formed, and I don't know if it will work. You may need to experiment a bit and test this. My understanding of your use case was something like below, and so I thought the nesting of lower level bullets (e.g. sub items) would prevent syncing them later in the output with their "parent"…

Let's confirm your use case, cover a solution approach, and then note alternate use cases. Your rule and diagram indicate the use case is: * Given there are 4 tasks (note: your rule seems to indicate these are sub-tasks issue types, but I will keep calling them "task" for consistency) * And 3 of them are linked as blocking…

If you write a field containing Jira markup to the audit log, you will see that bullets appear with a varying number of asterisks * (or pound signs #) and that heading levels are prefixed by h1, h2, etc. Those are distinct enough to allow splitting on a header first and then bullets. Although now that I think about it...I…

Hi @Matthew Rochman -- Welcome to the Atlassian Community! I expect this will be a case-by-case thing, and so you may want to create a new question, link to this one, and post images of the rule and audit log you are trying to improve. In general, using the project scope rules does not use up any global/multi-project…

When I tested this it was with Jira Cloud. Are you using Jira Cloud or Server/Data Center version? That image looks like it is from Server/Data Center's pro version (paid) of automation. The Server/Data Center help seems to match Cloud for the example showing this working. Let's try to write that smart value to the audit…

I re-tested with some similar text in the description field and it worked. Would you please post an image of your advanced compare condition component in the rule?

Please try the "Contains Regular Expression" option instead for that list.

Hmmm...this could be a brittle solution that might work: If you used heading levels (h1, h2...) in the Jira field, those could be used as split groupings, with the first split on h1 and then process (nest) the result with a second split on line breaks and h2 (or just lines) to add the additional necessary HTML. I…

Hi @Neil Wills I could predict some unintended consequences of hiding such a field... If the team knows this is their process (i.e. an engineering lead makes a high-level forecast prior to refinement by the rest of the team) why not just leave the field visible, as both an learning and conversation starter for improvement?…

I also meant "Notes" as a placeholder...I was thinking people were entering the details on the Confluence page, and instead it appears you mean there could be 1-to-many "notes" entered in that field below each first-level bullet. Correct?

It appears from the rule error that EQUALS = did not work, so perhaps try CONTAINS ~ in a stand-alone query first to see if that works for the text field: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/#Advancedsearchingoperatorsreference-CONTAINS-CONTAINS-- ("Account Type" ~…

Do you mean to add the * Notes list item after each comment line? If so, how about nesting within the iterator: {{#Release notes comments.split("\n")}} * {{.}} * Notes {{/}}

What type of field is Account Type? Perhaps this syntax would work better: "Account Type" IN ("New Lead Bookings", "Top of Funnel", "New Lead CSM/Ecomm", "New Lead TOF Restaurants", "New Lead Restaurants")

Hi @siond For a question like this, please consider posting images of your complete rule and the audit log, showing and details. Those may provide context for the community to offer help. Thanks! What is the type of your field: text, single-select, multiple-select, etc.? Kind regards, Bill

Hi @a_kim -- Welcome to the Atlassian Community! I doubt there is a "best practice" for this use case; instead what would align better with how your team works? For example, does the capability built by the user story always, sometimes, or never get released simultaneously for the three products: * always: consider how to…

Hi @Michael Fortunato -- Welcome to the Atlassian Community! I suspect the Release Notes Comments field is losing its form of Jira markup and then getting re-interpreted when added to Confluence. Have you considered splitting the field on line breaks and adding your own Confluence Markup for…

Hi @Ariel Eduardo Casiano García -- Welcome to the Atlassian Community! When you need to find the correct smart value for a field, please try this how-to article. Basically you find an example issue and then call the REST API with a browser to list all of the possible fields.…

Hi @Jeffrey Learned -- Welcome to the Atlassian Community! That feature is in development now for team-managed projects. You may watch/vote for the feature to see the progress: https://jira.atlassian.com/browse/JSWCLOUD-17195 Kind regards, Bill

Thanks for clarifying, Rachael. The Ranking field appears to be a custom field, and if your site admin added it the field should be possible to add on the backlog and board (cards) views. If you are using a Company-managed project, the project admin can add the field by selecting ... > board settings > card layout 

Hi @wabernathy It seems you want to do this to maintain visibility of an issue in one project (e.g. ABC) from the other (e.g. DEF). Rather than cloning (and synchronizing...) have you considered instead updating the board filter to include such issues in the DEF board(s)? You could add a special label (or other field) such…

Hi @Rachael Gresham That seems correct that the built-in Rank field cannot be added to the board or backlog views, and...I wonder: what problem you are trying to solve by displaying it? The Rank field contains the Lexorank value and is not very human-friendly to determine ordering of issues. Kind regards, Bill

Hi @Jürgen Heckmann That appears to be a known behavior: the {{createdIssue}} and {{createdIssues}} contexts are not updated in the main flow when an issue is created within a conditional part of the rule: https://codebarrel.atlassian.net/browse/AUT-1090 Kind regards, Bill

Hi @Ashraf What are the key performance indicators (KPI) you want to measure? Knowing that will help you decide if they are available with Jira's built-in features or if you should investigate other options: data export/reporting, pull data into another tool with the REST API, or purchase marketplace reporting/dashboard…

My apologies...it appears that in the year since I developed this approach (March 2021) that the rightPad() and leftPad() functions no longer accept a smart value as a parameter for the count. I'll experiment with this a bit to see if I can find a work-around, or if I am just missing something.

That appears to indicate that a site admin added another Story Points field at some point, and that caused the rule confusion. Or perhaps some Jira migration process caused it. Regardless of the initial cause, at this point I recommend submitting a ticket to the support team for assistance. Otherwise repeated changes to…

Hi @Firas Abdallah I do not know of anything built-into Jira to do this. What problem are you trying to solve by performing such an action? Kind regards, Bill

Hi @Stephen C Hauer One way to do this in an automation rule, for up to 100 items, is to create a source for an advanced branch from your counter field. Let's assume that is called {{issue.myCustomFieldCounter}} * Create a variable with an initial dummy value of NULL* name: varNull * smart value: NULL * Create another…

Hi @Thomas Alombro -- Welcome to the Atlassian Community! There are at least two open defects for this symptom: * https://jira.atlassian.com/browse/JRACLOUD-78845 * https://jira.atlassian.com/browse/JRACLOUD-78879 If either matches your situation you may want to watch/vote for it to see progress and potential work-arounds.…

Thanks for that information. Would you also include images of each Create Variable and Issue Edit component to show the details? That may reveal what is happening better. And have you tried writing the created variables to the audit log to confirm they contain what you expected?

Hi @Семён Жарычев -- Welcome to the Atlassian Community! You could call the REST API with a web request using the accountId, get the email address, and then send your custom message. Please note doing this means the user would get 2 emails per mention: one from the mention and one from the rule. If you want to try this…