Bill Sheboy Expert

Hi @Joanna Romańska -- Welcome to the Atlassian Community! Have you investigated using Automation for Jira to detect when the field changes and to set/send a notification? Automation for Jira is included in Jira Cloud, and there are free (Lite) and paid (Pro) versions for Jira Server/Data Center. Please discuss with your…

Hi @Muhammad Yunus -- Welcome to the Atlassian Community! What problem are you trying to solve with such a rule? How frequently are you changing subscription plans? Jira automation seems like it is meant to reduce work with frequently occurring activities and to reduce errors in repeated work steps. Best regards, Bill

Hi @Yuliia Maidanova -Alpha Serve- When recommending a marketplace vendor product, please ensure that you disclosure your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines for Marketplace and Solution Partners…

Hi @[deleted] -- Welcome to the Atlassian Community! Please take a look at this post on getting the information from cascading fields: https://community.atlassian.com/t5/Marketplace-Apps-Integrations/How-can-I-copy-a-cascading-select-value-with-Automation-for-JIRA/qaq-p/585395 Best regards, Bill

Yes, and...I also suggest... * Jira Admins have a DBA (not a DBE) background (i.e. experience / training / skill) in order to have productive conversations with people requesting custom fields. That could head off nightmares of storing dozens of critical data attributes in description fields, and trying to figure out how…

Thanks for that explanation, and here are more exploratory questions. :^) * Are the different teams working in one or multiple projects in Jira? If in one project, how do you distinguish the different teams: label, component, something else? * What is the scope of this rule: at a project level or global for all projects? *…

Perhaps you could change to the Default Text Renderer; however the field would lose most of the formatting and macro capabilities. https://confluence.atlassian.com/adminjiracloud/configuring-a-field-configuration-844500798.html…

Hi @leewarren The short answer is: no, and maybe. "No...and...": There isn't any grid-like edit for out-of-the-box software Jira projects. I believe there is such a feature for the business projects, and hopefully it will be added to other project types one day. Here's the business project…

Thanks for that information. Perhaps you could explain your use case further... When an issue is commented, the rule is triggered, and you send an email for a list of issues found by JQL. * This will send an email whenever any issue in the project is commented upon. Is that what you wanted, or did you want to email when a…

Hi @sarai.makni For Jira Cloud automation, Lookup Issues is one way to send the batch in one email, versus branch/scheduled rule to send multiple emails. Perhaps like this: * trigger: issue commented * action: lookup issues: with your JQL * action: send email, with the lookup issues contents, such as {{#lookupIssues}}*…

Interesting... that is why I was suggesting that how-to article. Basically you find an example issue which has your data, look it up with the REST API... https://<yourinstanceurl>/rest/api/2/issue/<issuekey>?expand=names And then search for your data and field name. If it is present, the smart value probably will work.…

Drew, I put your exact smart value string in the audit log, and it worked for me: {{#issue.labels}}"{{.}}"{{^last}},{{/}}{{/}} Then, I tried creating a variable, which I gave the name of varLabels, and then in another action sent to the audit log as {{varLabels}} and it worked again. Would you please post an image of what…

Hi @Ena Garner What have you tried so far in creating this query? This seems very specific to your use case, and so it is unlikely another community member has it pre-built. Perhaps posting your solution will give the community context to offer you ideas. If you have not created one yet, please look at these documentation…

Hi @[deleted] John has you on the correct track, and I suggest a small adjustment to add semicolon delimiters, except for the last value in the list: {{#issue.Stakeholders}} {{emailAddress}} {{^last}} ; {{/}} {{/}} But first, have you confirmed that value is the correct smart value of your field name? You may check that…

Hi @James Phillips Yup, that is definitely a limitation of the built-in, Jira interpretation of a control chart. And, you may only zoom in so far on the timescale and that may not be enough to separate them. Here is a suggestion to improve that effect: https://jira.atlassian.com/browse/JSWCLOUD-16665 One cumbersome…

Hi @Dan (Daniel) Newman No, not with out-of-the-box Jira. The JQL may use absolute or relative dates, but it is not a SQL and so you cannot do that type of query. There may be marketplace addons for purchase that support this. You could try using startOfMonth(-1) to reflect things like last month, or startofWeek(-1) for…

Hi @Tarak -- Welcome to the Atlassian Community! For company-managed projects (CMP), the custom fields are defined globally and shared and so use the same ID. However for team-managed projects (TMP), each one has it's own instances of fields created within that scope; so the same named field in two different TMPs will have…

Hi @karen.loomis -- Welcome to the Atlassian Community! You seem to be asking two different questions with your post title and the question contents: * can we dynamically start an issue once its predecessor has completed? * using issue block links, can we set the start date of an issue based upon the end date (due date?)…

Hi @Vikram Ingleshwar To reduce the line spacing a bit, please try using "shift-enter" rather than just enter between lines. Best regards, Bill

Thanks for that information, Alex. I am stumped, and I suggest that you submit a defect to Atlassian Support to see what they can find. They have more access to internal logs than customer users do. As site admin for a paid instance, you may submit a defect here: https://support.atlassian.com/contact/#/ Once you hear from…

I do not know how that is currently possible with built-in automation rules' JSON edit. After experimenting a bit with {{issue.parent.key}} and {{issue.parent.id}} (for a subtask) I was unable to change a subtask's parent. There is more to the relationship than just those fields, and so Jira needs to manage it. One…

I am glad that helped you. Please consider marking this question as "answered" to help others find solutions faster. Thanks! Regarding the field distinction, team-managed projects changed a lot as part of a code re-write, changing the mechanism for linking parents to children...and so causing differences like this. As I am…

Hi, and thanks for clarifying. You noted in your original question "...we handle automated tests with cucumber and selenium that we would like to link via API to JIRA" Automation for Jira can call REST API methods and respond to webhooks from other tools. I suggest you investigate the capabilities of the tools you note…

Hi, Katie. Sometimes the key for automation and custom fields is finding the smart value. Let's try this: use the log action to write just the field to the log, such as one of the following: {{issue.Code Reviewers(s)}} {{issue.code reviewers(s)}} {{issue."Code Reviewers(s)"}} If one of those works, substitute that into the…

Dave, are you using a company-managed or a team-managed project? If team-managed, those use Parent instead of "Epic Link", so please substitute that field in the query.

Hi @Drew Nedderman I recommend that you extract the labels into a Created Variable action, and log that to the audit log. That will help you diagnose what is happening. When it is working, use the created variable in your JSON update. Best regards, Bill

Are you using Jira Server or Jira Cloud? * Automation for Jira is included free in Jira Cloud * If you are instead using Server, there is a free Lite version of Automation for Jira. Only the Pro version has a monthly charge.

Yup, that is what I was suggesting, and I am glad that worked. Sorry my explanation was so long; I was trying to give you some context in case two rules didn't work and you needed to uncover "why". __Bill

Hi, Michael. Why would you need JSON to link them? Instead you could do the following: * trigger: whatever you select * action: create issue * branch: on created issue* action: create sub-tasks for created issue

Hi @katie.kurty Have you tried treating your custom field as a list? Perhaps something like this in the comment: {{#issue."Code Reviewer(s)"}} - [~accountid:{{accountId}}] {{/}} Please consider first writing to the audit log until you get your custom field name's smart value correct, and this should work. If you have…