Bill Sheboy Expert

Hi @Kitty Crawford -- Welcome to the Atlassian Community! Is your request for a team of people using the scrum framework? If so, what problem are you trying to solve by tracking the work of individuals rather than the team? Thanks, and best regards, Bill

Hi @brosenthal You could do that with Automation for Jira, updating the epics based upon the Sprint the children are in. (Or, go the other direction and update the Epic based upon children being added to a sprint.) Please look at this information on automation if you are interested in trying that approach:…

Hi @Margaret Hodges -- Welcome to the Atlassian Community! That is not possible at this time with Jira Cloud. Here is a suggestion from 2013 to add the feature. I did not find a more recent one. https://jira.atlassian.com/browse/JRACLOUD-34895 Best regards, Bill

Hi @Kim Dinh No worries; glad to try to help. When you loop over the issues, you only need the iterator stuff one time. Like this to iterate one time over the {{issues}}. {{#issues}} {{key}} | {{summary}} | {{status.name}} {{/}} And, I am unclear for the Server version if anything odd happens with pipe (|) processing. If…

Hi @Dominique Bastien -- Welcome to the Atlassian Community! I agree, and it isn't clear to me what problem they were solving with that design choice. Please consider looking at remaining work for the new issue view to see what improvements around Comments are planned under the sub-tasks.…

Hi @Tim Riches I am confused by what you are asking, as you note using both Kanban and Sprints (which are associated to Scrum use). If you are using Kanban, you could disable backlog use and all of the "to do" items would be in the left-most column of your board, and so always in view. If you are using Scrum, there is…

Hi @marie.mitchell I saw an older ticket related to this symptom which was resolved years ago. People have started commented on it again, and I suggest submitting a new defect to Atlassian support: https://support.atlassian.com/contact/#/ Once you hear from them, please post back here what you learn. Thanks! Best regards,…

Hi @[deleted] You are correct that you cannot nest branch statements to do what you ask for a 3-level branch: version issues, links to "feature request" issues, and then linked issues to the feature request. As alternatives, have you considered setting the fixVersion of the "feature request" issues as they are linked to…

Hi @Patricio Rodriguez -- Welcome to the Atlassian Community! Would you please post images of the settings you used for the gadge and the JQL used to obtain the listed issues? Perhaps there is a difference between them impacting the gadget. Best regards, Bill

Hi @Cheong sanghun and @Tobias Rettensteiner I believe the subtasksOf() function is only available in the purchased add-on ScriptRunner from the marketplace. If you do not have a scripting add-on, I do not believe there is a way to perform that query with out-of-the-box Jira Cloud. Best regards, Bill

Thanks, @Flavia Oliveira Well, that rules out Next-Gen issues with the different epic management mechanism. Would you please use the Log action to write the {{issue.epic link}} to the audit log? That will confirm the issue contains what you expect before trying to test it with the advanced compare.

Hi @Sarath That feature idea appears to be in the backlog: https://codebarrel.atlassian.net/browse/AUT-1623 Until that gets implemented, you may need to compute the business days diff by hand by checking for the holidays being in the date range. If you are using Jira Cloud, the Create Variable action could help provide…

Thanks for clarifying that information. If you are getting data by the REST API, the key value in the Epic Link should be uniquely matched to the epic. Which REST API call are you using? Perhaps if it is a saved filter the column just needs to be added. Or, you could use a different call to get all available fields.

@Dora Lukin for a date field work-around, you could try this: advanced compare condition for {{issue.myDateFieldName|0}} equals 0 What that will do is substitute a default of zero (0) when the field is blank or empty, and then test for zero. __Bill

Here are some suggestions to improve subscription emails, which you may watch or vote for: https://jira.atlassian.com/issues/?jql=project%20IN%20(JRACLOUD%2C%20JSWCLOUD)%20AND%20resolution%20%3D%20Unresolved%20AND%20summary%20~%20subscription%20AND%20summary%20~%20email%20ORDER%20BY%20Key

Hi @Chris Fortmueller I just noticed some capitalization issues in your smart values; these are often case-sensitive. Fixing those may help diagnose what is happening. * {{issue.vorheriger Status}} -- please confirm this matches the capitilization in the status names list * {{issue.vorheriger Status.Name}} should…

Hi @Flavia Oliveira Is this a Classic or Next-Gen project?

Hi @Arthur Bershadskiy Those old values in the sprint field help in some cases and not in others... How about this: rather than test on isStarted use a JQL condition test for the triggerIssue Key and sprint in openSprints() Also, how do you know which version to assign? Are you always using earliestUnreleasedVersion() or…

Hi @Bridget Thanks for the responses! Regarding the List, Boards, Forms, etc. colors... Background color changes are helpful. I was asking about issue and other item color improvement, data-driven on settings, fields, etc.. Some examples: * non-working days in a different color on calendars * color entire issues rather…

Hi @Kim Dinh Yes, Lookup Issues is in Cloud only. The equivalent in Server version is the smart value {{issues}} Please note the plural as this is a list. https://confluence.atlassian.com/automation/smart-values-993924860.html Best regards, Bill

Hi @Anne Saunders There is nothing built-in to do this, and you could build it yourself using automation rules. * Define what you mean by "percent complete" or progress * Add a text custom field, such as PercentComplete * Create an automation rule, triggered an adding a sub-task, to update the parent's PercentComplete *…

Curious behavior differences... For Next Gen, you may select anywhere (left to right) on the epic view's child issue list and drag-n-drop, changing the order. For Classic, you may only select on the left side by the key, and it appears as if it will re-order, and instead it opens the child issue, navigating away from the…

Hi @Flavia Oliveira In addition to posting an image of your rule, would you please describe the problem you are trying to solve with duplicate issues in two different Jira projects? Thanks! Best regards, Bill

Hi @Sarath In your sample JSON, the curly brackets are not all matched: * there is a missing close } for the first update * there is a missing close } for the overall expression Please add those and see what happens. Thanks! Best regards, Bill

Hi @Doug Levitt What do you plan to do with PlannedStartDate and PlannedEndDate, and when do you plan to use that information (relative to the sprint start timeframe)? For example, if you do not plan to do anything until after the sprint starts/completes, you could just set the values based on the trigger Sprint Started.…

Hello all, Looks good, and I am interested to see how these new features blend with existing capabilities over time. For example: * Will the List have definable quick filters? * Will the List have the ability to bulk update, without a navigation over to issues/filters? * Will the Calendar (and Roadmap) support non-issue…

Hi! There is definitely a recent issue with "IS EMPTY" and text fields, and I wonder if this issue impacts other field types as well. The apparent cause is once a field has been set and then cleared, a distinction is made between BLANK and EMPTY in JQL and the API. You may watch the progress of the fix for this issue here:…

Thanks @Chase Wilson Sorry to parse words; to confirm your statement, "...every licensed Jira Cloud user will be able to collaborate on Business projects at no additional cost..." * Did you mean every licensed Jira Core user (soon to be rebranded Jira Work Management)... or * Did you mean every licensed user of any Jira…

Hi @Jesse Pelton That syntax for JQL is working for me: "epic link" in ("EPIC-1") That second error message seems to indicate another field named "epic link", perhaps a custom field with multiple options: "The option 'EPIC-1 for field 'epic link' does not exist." Have you asked your site admin if there is a custom field…

I am glad that worked! And, I wish the rule editor showed better error messages before publish and after execution. Showing smart values as proportional fonts (rather than fixed) makes it very difficult to see issues too. :^)