Bill Sheboy Expert

Yes, however fields are defined at a project level for Next-Gen: https://support.atlassian.com/jira-software-cloud/docs/available-custom-fields-for-next-gen-projects/ Which I believe means you need to add them in each project, one by one.

Hey, Brad...Okay, I am stumped on this one. I found this defect/symptom which may be related to what you are observing: https://codebarrel.atlassian.net/browse/AUT-1769 It states that when parallel sprints are enabled, Next Sprint cannot be accurately determined. So I wonder if the same is true for active sprints. Here is…

Thanks for clarifying your use case, which is to both show the presence and absence of data for the 10 markets. That confirms for me that you will not be able to do this with out-of-the-box Jira on a dashboard. Instead you would need a marketplace add-on for dashboards, or perhaps use the Atlassian Excel add-in or Google…

Hi @Valentin R. Your question seems like a good idea for some circumstances, and... After checking a bit, I did not find anything obvious to query for this distinction. There are fields which should be unique to each type (e.g. Story Points vs Story Point Estimate), but there are no restrictions preventing the mis-use in…

Hi @Jason Thompson Have you already solved this question? If not, I wondered about two things: * Have you confirmed the custom field ID you are using matches that field name? Your admin can check that, or you can use this how-to when you need the smart value name for a…

Thanks for that information, Brad. First thing: branches are a bit slow in automation rules, even when they get in-lined. Consider replacing that structure of branching on the current triggering issue to use a long If/Else condition instead. Plus, the rule will be smaller. Next, I see no condition on the issue type after…

Hi @Brad Is this for an Issue Created trigger? If so, I wonder if this is related to the known race condition where the issue isn't fully available when the event is caught by the trigger. If so, please try to add a Re-fetch action immediately after the trigger and before any other actions. If not, would you please post an…

Hi @Lou Sacco Deleting stuff from Cloud is problematic, as there is no "undo". We solve that by adding an "Abandoned" custom field and remove all of those from filtered board views. We may find them later with a simple search. Extending that idea to your use case, you could add a label, component, or custom field to…

Hi @Gantner NV One more thing to check: in your related issues JQL, please check that the case of the issue type and status values match your definitions. I have seen situations where something like "closed" and "Closed" behave differently. If that doesn't help, I suggest you submit a ticket to support so they can look at…

Thanks, Chris! And...I continue to be puzzled why the API (used by the automation engine) renames some smart values plural for list fields (e.g. fixVersions) when it is not the same for the JQL. Or worse, changes the names entirely or changes spacing for multi-word values. Hopefully the documentation will one day include a…

Hi @Jeff Davis These many-to-many relationships are difficult to report on from out-of-the-box Jira. Sprint seems to be the exception where you can use the Two-Dimensional dashboard gadget to do what you ask...unfortunately that gadget doesn't support links or this would be easy for you. There are probably marketplace…

Hi @ben_d -- Welcome to the Atlassian Community! Just checking: are you using a Classic or Next-Gen project? Best regards, Bill

Hi @Roelof Reitsma I found this open defect for this symptom, which you may vote for/watch: https://jira.atlassian.com/browse/JRACLOUD-72230 The work-around obivously isn't going to help after 31 March: "switch back to old view..." Given the absence of other work-arounds or listed work in the New Issue View ticket, I…

Hi @Mabbu prasad The short answer is: no, you cannot do this with out-of-the-box Jira features. The information shown on Jira dashboards almost always relates to issues (epics, stories, etc.) The exceptions are gadgets like placeholders/dividers. The country list you note would have no association to issues and so couldn't…

Hi @Dawn Cooper To help the community provide you suggestions, I recommend you list some of your use cases/features you need. And, perhaps perform a browser search of the needs to help you align what you are looking for to the terminology used by these tools. Otherwise any recommendations you see from fellow users or…

Hi @Howard Nedd This may be an API issue or a "catching up" issue in the code base. I see a suggestion to make the Insight fields available as triggers: https://codebarrel.atlassian.net/browse/AUT-1523 I did not see any suggestions related to Elements Connect fields. You may want to try this technique to learn if the…

Hi @Mukthadir Sikdar What have you tried thus far for your use case? As this is a commonly requested need, Atlassian has provided both examples and a template. For an example, please look here: https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/140671 For a template to get you started, please…

Hi @Gero Kassen For your specific question, I do not have a recommended marketplace addon for this need. If you search for "sprint" on the marketplace there are probably several, although they may do this by dashboard charting rather than making the data available for searches. To do that, you could consider a JQL add-on…

Hi @Pam Walters Here are two of the ways to do this: call the sprint report from the REST API or build your own tracking using automation rules. For the REST API, the resulting information is in JSON so you would need to search the results for your answer. To do this with the REST API, enter this URL into a browser window,…

Hi @Bud Herz Sorry to be the bearer of unhelpful news...For the good questions you are asking, most of the information is in the change logs for issues. However with out-of-the-box Jira features that info cannot be easily queried. There are marketplace add-ons for JQL, status analysis, and dashboards which make such…

How about a no-addons required, histogram plot of issue data? TL;DR: Using lookup issues, format and RegEx functions, count the issues meeting your criteria. Padding functions add the histogram data points. This works for up to 100 issues (due to the rule execution limit), and can only access the fields within the lookup.…

I am glad to hear that helped!

Thanks for that information. Have you tried to remove that last user restriction to see the results, regardless of the rule's executing user? I am wondering if this is one of those edge-cases where interactions between rule execution and workflow is causing a problem.

Hi @Ray Shekane I am unclear what you mean by expand on the options. Perhaps doing a browser search on some HTML examples for your use case will give you ideas on the markup used to meet your needs. Thanks!

Hi @Igor Ordoñez Without a more in-depth discussion about how your team works, I suggest the answer is "maybe" if you are using this a forecast and not as a committed estimate. You might do this with automation rules or calculated fields with a scripting add-on product from the marketplace. Often teams that work together…

Hi, @Hunter1428 Great find! Two things to try: Under the email options, I disabled "Convert line breaks to HTML line breaks" and it removed the extra line breaks when I used {{issue.description.html}} Next, if that doesn't fully work, you could hack-up the converted HTML: * First, echo {{issue.description.html}} to the…

Hi @Naveen Kumar -- Welcome to the Atlassian Community! You can not do that with out-of-the-box Jira JQL. You would need a marketplace addon which can enhance the JQL functions. If you have just one defect to consider, I suggest instead reviewing the history for the defect directly to find what you ask. Best regards, Bill

Sorry I missed the issue here..it appears that the automation rule engine does not yet process the wiki markup from the fields in Jira. Here are the related things in the suggestion backlog: * https://codebarrel.atlassian.net/browse/AUT-2050 * https://codebarrel.atlassian.net/browse/AUT-1684 As a work-around, I have…

Hi @Elizabeth Dutton Are you able to use incoming webhooks to do that? Please take a look here for more information for Jira Server/Data Center: https://confluence.atlassian.com/automation/triggers-993924804.html/#Triggers-incomingwebhookIncomingwebhook

Hi, automation rule writers! I added a suggestion that you may be interested in watching: log a warning error when the processing limit (100) would have been exceeded. https://jira.atlassian.com/browse/JIRAAUTOSERVER-238 Thanks, Bill