Bill Sheboy Expert

Hi @Florian Warncke -- Welcome to the Atlassian Community! I am guessing you are trying this in an automation rule, correct? If so, when you nest smart values you do not use the extra curly brackets. Please try: {{issue.timetracking.remainingEstimate.minusSeconds(worklog.timeSpent.seconds)}} Also, when asking questions…

Hi @Tim Bainbridge -- Welcome to the Atlassian Community! Jira Cloud cannot do this out-of-the-box as the JQL is not a query language with JOINS. So... How many times do you need to perform this query? * Lots of times: probably need to buy a scripting add-on from the marketplace or build your own merge/join by pulling data…

Hi @Kaspars Kalnins Nope, I am not an Atlassian employee; just a fellow user trying to help. When I have a defect to submit I also need to do that through my site admin. As you have already recorded the symptom and repro steps, your site admin should be able to quickly create the defect and get a support person in touch…

Oops... looks like this is version related: * Tried a rule with Affects Version field: same symptom * Tried a rule with Last Released Version: same symptom * Called the REST API manually and all versions are still returned, including the correct attributes values for released @[deleted] did you submit a support ticket on…

Hi @[deleted] In addition to John's questions, would you please add a screen image of your releases (version) page? Thanks, Bill

Hi @Kevin Ketchum Are these suggestions what you are requesting? * https://jira.atlassian.com/browse/JRASERVER-70611 * https://jira.atlassian.com/browse/JRASERVER-68765 Best regards, Bill

Hi @[deleted] If I understand your question, you have "job qualification" (selection of work/refinement) prior to the start of development. And, you do not want to have that on the development board/sprint as that would impact the team's velocity. If that is correct, you have a few options: * Do not track the work of…

Hi @Sebastian Krzyzanowski -- Welcome to the Atlassian Community! Some words of warning here... The rule components in Branches execute asynchronously and independently. That means there is no guarantee the first branch in your rule will finish before the second one starts. For your rule, that could be a problem because…

Yes, and... for your question #1 Stories can be the parents of Sub-Tasks, not of Tasks. Best regards, Bill

Thanks for that information. If you believe this is a different defect, you may ask your site admin to submit a support ticket to Atlassian to investigate: https://support.atlassian.com/contact/#/

Hi @Ben Sullivan Just to confirm, are you using automation rules for this transition or are you using workflow transitions? If workflow, take a look at what @Eoin suggests. If automation rules... to find the automation audit log... * On your board, select the lightning bolt * Select view audit log * Find the recent…

Hi @Sara Creenan _M_T_ As others have noted, that is not possible with out-of-the-box Jira. What we do as a work-around is 2 exports: * Export all epics we care about as CSV, adding them to a spreadsheet tab (EPICS), and sort by Key * Export the stories we care about as CSV, adding them to another spreadsheet tab (STORIES)…

Once you hear back, please post back here so others can see what you learned from support. Thanks!

Hi @Kaspars Kalnins It appears there are two open "suggestions" related to this symptom in the public backlog. You may watch/vote for them here. One is very old, indeed! https://jira.atlassian.com/browse/JRACLOUD-2169 https://jira.atlassian.com/browse/JRACLOUD-67875 Best regards, Bill

Oops, and sorry, Greg. Looks like all of the radio buttons are missing on that page view, per the server automation documentation. My next suggestions would be to clear the browser cache, try another browser type, and if the radio buttons are still missing something is broken (and probably worthy of a support ticket).

Hi @Anders E. Jensen and @KHack I am wondering... Isn't the CHANGED AFTER operator date-based and also equates to greater than not greater than or equal to? So using "2020/02/01" could allow things un-Done on 2/1 to slip through, right? Or is the time implied to be 00:00 for these? Would this be better? status WAS Done…

Hi @JJ DeBenning -- Welcome to the Atlassian Community! For Next-Gen projects, there are only the built-in groupings at this time, and not JQL-based swimlanes to group by Classes of Service, as in your example. There is a suggestion to add this feature, and you may watch/vote for it here:…

Hmmm... Reading the vendor's documentation, I see there is a setting for "Number of emails" to control the behavior you are seeing. Did you check that one? https://www.midori-global.com/products/better-pdf-automation-for-jira/server/documentation/

Hi @Celestyna Banaszak -- Welcome to the Atlassian Community! You can do that using automation rules, with the Issue Moved trigger to detect the condition and then add the Watchers you need. If you need to further confirm that the source project was ENGBL, you may add a condition to check the previous value of the key…

Hi @Greg Bailey Full disclosure: I have not used that add-on to create PDF files before. How does that add-on accept input to create the PDF? I believe in server version, there is a smart value of {{issues}} (note the plural) that contains the result set of a JQL. Can that be used? If not, you may want to ping that add-on…

Hi @Alex Degregori Looking at your rule, when the Custom Sprint field changes, you are trying to set the Fix Version to the previous values of the Custom Sprint field. Is that correct? First thing, I suggest putting in an audit log action for the value you are trying to set to the Fix Version. That will confirm if the…

Hi Audrey, Please try to set the Epic Link to the Current Issue when you create the new one. If that works for you, please consider marking this question as answered. That will help others in the community find solutions to similar questions faster. Thanks, Bill

Hi @Ben Sullivan -- Welcome to the Atlassian Community! As you already have a rule, please post an image of the rule and the audit log for an execution which did not work as you expected. That will give the community more information to try to help you. Thanks! Best regards, Bill

Thanks for that information. Please take a look at the dashboard feature and gadgets, especially the two-dimensional filter gadget. Those may help provide the information you need better than a Gantt chart. Best regards, Bill

Hi @Audrey Artis -- Welcome to the Atlassian Community! You are describing a case where you want to trigger a rule from one project, create a new issue, and link it to an epic in the original project. Is that correct? If so, you definitely can do this with an automation rule. Because this rule touches multiple projects, it…

Hi @Jayapriya Kannan -- Welcome to the Atlassian Community! Would you please provide a bit more detail so the community can help? * When you note "all the tickets but does nor display on board" what do the not displayed issues have in common? Or, is the board completely empty even though the filter works? * Are you using a…

Hi @Konstantin What problem are you trying to solve with this request? What would you do with this information if you had it? There are no out-of-the-box, built-in Gantt report capabilities in Jira cloud, standard version. At the project level, there is a roadmap which can display epics based upon their planned start and…

Hi @Krupa Savjani -- Welcome to the Atlassian Community! Agreeing with what @Trudy P Claspill suggests, please consider the problem you are trying to solve: improve visibility with you assigned to two teams at once leading to reduced capacity. You note that one of the teams is using Scrum, and so cloning/showing issues…

After my testing, I got this to work by keeping all of the stories in synch for Start Date and Due Date, and so "last wins" helps. Thus when you need an earlier (or later) Start Date, you change one story and it updates everything. If synchronizing the stories' date values does not match your use case I do not know how to…

Thanks again for clarifying. The challenge with your use case is iterating over all of the stories to find the earliest start date (or latest due date). Automation rule execution *within* a branch is non-deterministic, and so you cannot rely upon execution order or even use of temporary variables. Until one or both of…