Bill Sheboy Expert

Hi @Russell Tysoe -- Welcome to the Atlassian community! Try this for JIRA Cloud so the names are displayed rather than "user". This is an example for assignee. [~accountid:{{assignee.accountId}}] After the user/privacy changes, the id is the thing you need to link to the user. Best regards, Bill

Hi @Amy Bass It sounds like you may be missing a piece of your rule to access the items associated to the version. (Please post an image of your rule if I am missing something.) This can happen when you have placed your action *outside* of the branch structure. So, your rule might look something like this: * Trigger:…

Hi @rupa_srivastava Several recent community posts indicated timing issues with the create issue trigger. To avoid problems consider adding a re-fetch action. For your rule, it would flow like this: * Trigger: create issue * Action: re-fetch the issue * Condition: if it is one of the issue types you wanted * Action: edit…

In that case, if you know the user name, just type it in. For my company, the type-ahead would trigger when I started typing either the user name or the email address. If it still doesn't work, something else is happening. Of note: I find the type-ahead does not work later in a JQL expression when there are any earlier…

Hi @Charles Caldwell To delete label, it must be removed from all instances of usage on issues. Then it will no longer be visible. Best regards, Bill

Hi, and that is curious. I tried both of those before I posted them, and I just tried again and they both worked for Cloud. Don't use quotes for the username. Or, just start typing in the name and let type-ahead search help. When you use type-ahead it will replace the name with the long alpha-numeric string.

Hi @Mehran Thanks for the additional information, but I am now confused what you are trying to accomplish. I can tell you that JQL is not SQL; it is much simpler. It seems you are trying to form a complex query with joins that JQL cannot perform. And so, the REST API couldn't call such a query. To form such a query you…

Hi @Michael Regarding default values, I have only used the inline/smart value method noted, not in the JSON. Try experimenting around with the quotes to see if that is the issue, or see if you can learn more here: https://support.atlassian.com/jira-software-cloud/docs/what-are-smart-values/ And, here is the documentation…

Hi @Jim Cloughley Looks like this is a known bug: XML files in Jira Cloud backup are showing a wrong modified date https://jira.atlassian.com/browse/JRACLOUD-69019 Best regards, Bill

Hi @Suman Boro -- Welcome to the Atlassian community! To do all of the things you are asking about, you would need one of the marketplace add-ons to enhance version management features. Without buying add-ons, you could... View the releases on their page to see progress. Look here for more…

Thanks for the information... A JIRA board is a view of the backlog, using a filter and a selection of columns and status values. A sprint is a collection of backlog items. When you have multiple boards for one project you need a way to indicate the items on each board. For example, perhaps each team has a specific…

Hi @Mehran -- Welcome to the Atlassian community! Have you tried to from a JQL query and then call the REST API for it? Maybe something like: project = myProject AND issueType = Epic AND fixVersion = myVersion ORDER BY Key Then look at the examples here to make the REST API call for the query:…

Hi @Prasang Singhal -- Welcome to the Atlassian community! I believe that formatting may not work at this time. Please see this defect to see if it matches the issue you are seeing: https://jira.atlassian.com/browse/JRACLOUD-72071 Best regards, Bill

Hi @Gui Ávila Teams normally add items (one or many) to a sprint from the backlog view. If you are able to quickly identify them using the filtering on the backlog view, you can select team all and right-click to add to the sprint. Best regards, Bill

Hi @Saadoon Ameer I am confused by your question, so I am hoping you can clarify a bit. A JIRA scrum board is normally used by one team, and provides a view of the backlog for one active sprint. (managed by the board's filter) If there is a different scrum team, with a different sprint, why wouldn't they have their own…

First, consider viewing the activity for an item you believed changed status. It will show who/how the status changed. If it was automation that made the change... To check for the rules, go to project settings, automation. That will show you if there are any rules enabled for the project. If there are global rules, they…

Hi @Michael I have noticed some odd behaviors when fields are empty/nil, causing rules to either fail or show false success. To work around this you could: * Use the default field handling for empty fields: {{somefield|somedefault}} * Use a if/else structure to explicitly set a value when the source is empty Best regards,…

Hi @Colleen Bordieri I just tried your scenario with a classic project in Cloud version, and it worked correctly for me: start with 120 pts in sprint, add 2x5 pts and 1x3pts = rounded up to 11% scope change. So, perhaps there is a different server version issue. I found two open defects for server that seemed related you…

Hi @Huey van Zijl An update: another community member saw a similar issue with the edit/copy not working. They solved that by adding a re-fetch action to solve a potential timing problem where the created issue does not yet have the parent link. So, your updated rule would be: * Trigger: issue created * Action: re-fetch…

Thanks, Pete. I am uncertain what else to check in this case. If no one else posts ideas for you, consider submitting a support ticket to see if Atlassian can figure this one out: https://support.atlassian.com/contact/#/

Hi @Ahmed Alghamdi Thank you for clarifying. There may be a marketplace add-on to enhance version handling, as what you are asking for doesn't exist in JIRA. Do you assume each build will be in the next major release...and after that major release deploys, you repeat? If so, you could try this: * Add a custom field for the…

Hi @Simmo Yes, it was also a create issue trigger. That was my thought as well: timing condition. I suggested adding a condition check for issue type, as above, and adding tracing statements (debug or comments) to confirm the source data availability. If that doesn't work out I will suggest the refetch next. Thanks for the…

Hi @Ahmed Alghamdi With out-of-the-box JIRA, you could create a filter and subscribe to it. Here is the how-to for server version: https://confluence.atlassian.com/jira064/receiving-search-results-via-email-720416706.html If you have an add-on, like the automation rules, you could also make a more customized report. There…

Hi @Abin Joy -- Welcome to the Atlassian community! Using the search that @Sivarama Krishna K suggested showing the Sprint field, you can narrow the list by only looking at issues which have be in closed sprints: project = myProject AND sprint IN closedSprints() ORDER BY Key And, when you want to see items in previous and…

Hi @Pete Burns Have you tried the JIRA Admin Helper for notifications to see if it can figure it out for the user? Please look here for more information: https://confluence.atlassian.com/adminjiracloud/jira-admin-helper-818578850.html Best regards, Bill

Hi @Christopher Leach Please try the following for status and assignee. For comments, I believe you would need one of the marketplace add-on tools to enhance JQL. project = myProject AND status CHANGED BY "username" project = myProject AND assignee WAS "username" OR assignee = "username" Best regards, Bill

Hi @Michael Walker Based upon the documentation for the "control chart" report, it would include the date range and status values you select. To include items which you want to measure that span sprints, you would include the relevant data ranges.…

Hi @Pedro Catoira When you have multiple status values assigned to a column on the board, you select which one to use when you drag-n-drop the item. Are you using any workflow or automation rules that might be changing the status? Best regards, Bill

Hi, @Evan -- Did any of the fields copy from the parent? Also, please consider adding a condition after the trigger to ensure that the issue type is a sub-task. Otherwise, other issue creates will attempt to process this rule's copy fields. Hi, @John Funk -- This is the second post today I have seen for automation rules…

Hi @Colleen Bordieri -- Welcome to the Atlassian community! Have you reviewed this documentation for the gadget? It essentially uses the estimation method for your board and calculates using the add/removed items since the sprint started.…