Bill Sheboy Expert

Here are the two defects for this symptom. You can watch them and/or mark that they impact your team. * https://jira.atlassian.com/browse/JSWCLOUD-21154 * https://jira.atlassian.com/browse/JRACLOUD-70797

Hi @Daniel Covill My understanding is that symptom can happen when you use any Team-managed (formerly called Next-Gen) projects in you instance. Are you doing so? If so, the cause appears to be each project has it's own version of each status, and so CHANGED, WAS, etc. get confused. The work-around is to use the specific…

Hi @Tim Bainbridge Have you tried: {{issue.customfield_18700.displayName}} Here is a reference for the user smart values which are usually available: https://support.atlassian.com/jira-software-cloud/docs/smart-values-users/ Best regards, Bill

Hi @Paul Cooper Thanks for the nice step by step write up! Two suggested improvements: * If you always need the epic total to be numeric, and it is possible for the stories to all have no story points, consider adding a default value to the sum: {{lookupIssues.Story Points.sum|0}} * This rule works for Company-managed…

Hi @Daniel Eads What is the purpose of having an indicator for "Atlassian Recommended" answers to questions which can displace the voting provided for the community for other answers? That mechanism seems redundant and to violate the spirit of a community-based support forum. Thanks for any information you can provide on…

Hi @Marcus Fredriksson -- Welcome to the Atlassian Community! There is no way to do that query with out-of-the-box JQL. You would need one of the marketplace add-ons for JQL, some are paid and there might be a free one to do it. If that isn't an option, you could investigate using automation for Jira and custom fields to…

Hi @Jaipal Singh -- Welcome to the Atlassian Community! The issues belong to a project, and the associated workflow for the issue type within that project. They cannot have a different workflow by displaying on a different board...a board is just a view of issues using a filter. * You seem to be describing that there is…

Hi @Domantas Giedraitis -- Welcome to the Atlassian Community! Seems like a great feature to have built-in; sadly it is not. There is at least one suggestion to add this: https://jira.atlassian.com/browse/JRACLOUD-62416 There appear to be several add-on products in the marketplace. I haven't used any of them, so ponder…

Hi @[deleted] You may find this documentation useful; it describes the advanced JQL features like CHANGED: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-functions/ Best regards, Bill

Hi @Patricia Albuquerque For Jira Server, there are two versions of Automation for Jira, the Lite (free) and the Pro (paid). Here is the comparison of the features: https://confluence.atlassian.com/automation/getting-the-right-version-993924597.html It shows that the Field Value Changed triggers is only in the Pro version.…

Sorry as I do not have knowledge about EazyBI. I suggest searching their documentation and for other solutions in the community to see what you can find: https://marketplace.atlassian.com/apps/1211051/eazybi-reports-and-charts-for-jira?hosting=server&tab=support…

Hi Anna, I just replicated your steps and learned something new: indeed you can have a sub-task assigned to an epic for some reason. Curious... What I did to fix this is * use Move from the ... menu to move the sub-task's parent back to a user story * use Convert to Issue from the ... menu to change the sub-task to a user…

I am glad to hear that worked! The way we solve the time zone issue is to adjust it before the condition test, rather than hard-code the altered time values. That prevents issues with time changes for DST and data entry errors. For example: {{issue.created.convertToTimeZone(issue.reporter.timeZone).format("hh")}}

Thanks, Josh. At this point I think you have two options: * If you only needed this one time, run the queries separately and merge the results in a spreadsheet after exporting * If you regularly need this query, talk to your site admin to submit a support request to Atlassian. Perhaps the support team will see something…

Thanks, David. Just to confirm, neither of these work, correct? * {{issue.customfield_10048.emailAddress}} * {{issue.customfield_10048.emailAddress.value}} Is this a Team-Managed (formerly called Next-Gen) project? If so there appears to be an open defect for the User Picker field access to the emailAddress attribute with…

Hi @Jaipal Singh -- Welcome to the Atlassian Community! Have you tried doing it from the all boards list? myCompany.atlassian.net/jira/boards Select create board > select a type > then select to create from existing saved filter Best regards, Bill

Thanks for the info, Mikael.

Hi @anna.brooks Would you please post some screen images of what you are seeing? And, is this a Team-Managed (next-gen) or Company-Managed (classic) project? I have not seen a sub-task directly assigned to an Epic before; it always belonged to another issue type (story, task, bug) which was then associated to the Epic.…

Hi @Derek Guzenski -- Welcome to the Atlassian Community! Would you please post images of your automation rule and an audit log entry showing a case where you expected the value to change? That will provide more context for the commuunity to offer ideas. Thanks! Best regards, Bill

Hi @CHANDRASEKRAN THIRUMALAISAMY -- Welcome to the Atlassian Community! First thing: I do not think that query by status will answer the question you have unless only one person does the work represented by each status. If you check by status, it would be something like this: project = myproject AND status CHANGED FROM…

Hi @_A9_ William Kennedy For the Cloud version, Automation for Jira (A4J) has an export and import capability for rules to JSON that the site admin can use. Is that a feature in the Server version you could try? Best regards, Bill

Thanks, Andy! Just to confirm, what is the recommendation: to let the transition complete without intervention for an instance that has both old/new, or to use the site admin feature to switch everyone? That is, I am trying to understand when an instance has both new/old if there is an underlying issue with the instance.…

Hi @Danut M _StonikByte_ Thanks for the article and add-on! Several of our teams use your product to help make workflow issues more visible. Here are a few, "yes, and..." items for dashboards using Great Gadgets: * We use the Issue Formula Gadget to make work in progress counts (WIP) visible. Set next to the Control Chart…

Hi @Mikael Sandberg I agree with your recommendation about the custom field, and I wanted to ask a follow-up question: Are you certain the issue transition automation trigger only catches the event after the transition is completed (persisted)? That is clearly not true for events like issue creation, which have racetrack…

Hi @Manuel Maldonado -- Welcome to the Atlassian Community! You can also do this with an advanced compare and regular expression check. Please see this post for details: https://community.atlassian.com/t5/Automation-questions/Assigning-round-robin-according-to-the-hour-of-the-day/qaq-p/1651142 Best regards, Bill

FYI for the possible permissions cause, there is a documentation page for Server that recommends using the guided "Where's my field" technique to try to solve it. That should be the same approach for Cloud version. https://confluence.atlassian.com/automation/solve-unknown-fields-error-in-the-audit-log-993924707.html

Thanks for clarifying that! The only time I have seen that error for automation was when the created issue changed/set a field which was not visible on the views, or a permission error for the field and the Automation user. As you are not changing the parent that seems unlikely for this case, but could be worth checking…

Hmmm... that is curious. The icon for both the trigger and new issue types looks like they are sub-task types, which I why I thought there was a parent error. Do you have any workflow rules?

Thanks, Logan. Did you check if there any workflow restrictions/rules on the target project? Also, this appears to be copying data from one custom sub-task type to another custom sub-task type. Is that correct? And if so, which issue is the Parent of the newly created issue, as that could be where the error message is…

Hi @Andy Heinzer Is that the intention of the "fix" (move everyone to new-view) or is there still an issue with people still being on old-view, and they are being left on it for some reason? (e.g. closing the feature gaps) And, does this fix address the missing Labs enable/disable option? I wanted to check these things…