Bill Sheboy Expert

Hi @[deleted] -- Welcome to the Atlassian Community! Are those two fields custom fields? On the board, if you want to add Quick Filters to find the issues with (or without) links, you can do that with the ... menu at the top-right side of the page > Board Settings > Quick Filters. You need to be able to write JQL to find…

By the way... this method *could* return multiple issues satisfying the trigger and JQL, so you have a couple of choices: a) Use a branch to iterate over the issues, sending an email for each. Given your problem description, this seems like the best approach to confirm that the comment is empty by putting it inside the…

Hi @Nawoda Herath What problem are you trying to solve by tracking what you believe to be the "no of bugs per the original developer"? What if the original developer is not the source of the defect? Perhaps instead there is a process issue, lack of work/knowledge sharing, validation error, etc. creating the situation of…

Hi @Marc Pincince You are correct that this appears possible using the private APIs to alter swim lanes, and public REST APIs to create project/board/filters etc. I agree with John on the time savings; unless you are regularly standing up/tearing down projects, this may not be worth the effort. And, I believe the…

Hi @David Rodriguez Torrontegi I do not believe that is a feature for Next-Gen yet. There is a suggestion to add it, which you can view and vote for here: https://jira.atlassian.com/browse/JSWCLOUD-17277 Best regards, Bill

Hi @Josh Allen Instead of using the transition trigger, you could use the schedule trigger, and check every X minutes (or hours, or whatever). Add a condition after the trigger to confirm that the issue is in progress (or use JQL in the trigger to be more efficient). Maybe something like: * Trigger: scheduled every 24…

Awesome; I am glad that helped you. __Bill

Hi, For the diff function, the earlier value comes first. Trying what John suggests, you would use: {{issue.Pull request opening date.diff(now).minutes}}

Hi, As this is already a date/time field, you may not need the .value part. I didn't need it when I use custom fields of that type with smart value functions. Best regards, Bill

Hi @Casey_Jones How about two swim lanes: the next, un-released version and all the others? You could make a query for that which would not require updates. As versions are released, the next would shift up on the board. fixVersion = earliestUnreleasedVersion() As a reminder, the "next" release is always the last one on…

Yes, and... the key is the triggers. If I understand the question, when #1 rule triggers, you want to prevent #2 rule from triggering, correct? The events used to trigger the rules are what you want consider. Is there something in common which could trigger both? If so, how can you make that unique enough to prevent the…

Hi @Season Hughes Without add-ons, a simple method you could use is card colors and queries to highlight a card, such as with: NOT status changed after -1w If you have automation rules, you could instead use a scheduled query and set the Flag to Impediment, which would show the flag indicator on the issues. To learn more…

Hi @[deleted] Thanks for the follow-up information. I completely understand the maintenance issue. Depending on the complexity of your definition of completeness, you may be able to create generic rules that your site admin just copies to projects. That could lower the effort costs. If you frequently change your definition…

Probably not, although given this is Next-Gen it could get focus sooner. I've found good ideas and defects in the public backlog for JIRA that are 15+ years old! As always there are more good ideas than capacity to implement them. You could try to fill in the feedback form on the JIRA UI, and select the box to join the…

Hey @JasonB3 I just found two open defects that could be what you are facing, as it appears the subtasks cannot be consistently accessed via JQL for a Next-Gen project. Please check these two defect to confirm how they align with what you are seeing: https://jira.atlassian.com/browse/JSWCLOUD-18398…

Nope, you are off track on the story points issue. For NextGen, they decided to use a different field. It is not a naming issue; it is a design choice. ;^) For NextGen, I recall that each project also uses its own status values. So, let's go more generic and try the category of the status to see what you get: project =…

Yes, and... that pop-up is starting to get annoying. ;^) It displays immediately upon posting an answer to a question which was not yet answered... And, when viewing an already answered question, it must be dismissed before you can comment. It never provides an opportunity for the reader to look over an item before…

Hi @JasonB3 Of note: JQL is not an actual SQL (ISO or otherwise). It appears to be a subset of a query language solely for the purpose of filtering for boards and reports. Are you certain about the issue type you are using? For example, what do you see when you try this query instead, substituting your project name for…

Hi @Karan Khiani -- Welcome to the Atlassian Community! There is no changelog data for the Version or Component yet, per some information in other posts from Atlassian folks. You can at least see a version changed using built-in functions to create an automation rule which watches for any changes to a Version and notifies…

Hi @Kirkie I think you are answering this question from the context of an issue, and not from changes made just to a Version's fields. Best regards, BIll

Hi @Petter Gonçalves Thanks for that information and explanation. Of note, I experimented and when I select "No" for not helpful, I do not see a text box. Instead I get a green checkmark indicating "thanks" and the pop-up then dismisses. __Bill

Hi @Earl McCutcheon Thanks for the info. The link you provided shows as invalid/blocked for me. Would you please update it? Will that information show other triggers which have timing issues? Regarding your question about details for race conditions, I know of two specific scenarios: * Create Issue * When an issue is…

Tom, you note that reporter will not work. Is there any other information in the issues that is unique to items created by the email-generated ones? If not, could you update the handler to somehow make them distinct, and so identifiable by the rule? The other approach is to flip this problem around: * When an issue is…

Hi @Assaf Shimon If you are not using Scrum with JIRA, you are using Kanban, correct? Rather than velocity, you could measure throughput: count of completed items per time interval. You could show that on a Dashboard with the two-dimensional gadget, for Fix Version and Issue Type. If you still want to measure sum of story…

Hi @Henry Yei How about this approach... * If you can extract the issue key you plan to link to with your expression, * Store that in a variable with the action Create Variable, such as {{var}} * And use an If/Else structure to only add the link when not found using a JQL condition (in the Else clause). An example JQL…

Thanks for that info... Some fields behave differently with different JQL syntax. If you post your full JQL statement, perhaps that will help the community offer ideas. __Bill

Hi @Cosmin Moldoveanu -- Welcome to the Atlassian Community! Please consider trying IS EMPTY rather than = EMPTY? Also, JQL is not really a SQL, ISO compliant variant. It has some common syntax elements but not all of them. Best regards, Bill

Hi @Kathleen King -- Welcome to the Atlassian Community! My short answer is: I think so. I am not quite understanding the workflow you are describing, and it seems to be: * Based upon some information in an issue, you believe you know who will help deliver it * Using that information, you create specific sub-tasks,…

Hi @Romain VELON I believe that you can use the temp variable action to save one field and compare to another. Here is the explanation of the variables action: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Create-variable-New-component/ba-p/1448118 Your rule might be something like: * Trigger: field…

Yup, what @Mikael Sandberg said... * Trigger: issue created * Action: re-fetch (for safety to handle race condition errors and un-populated fields in the issue) * Condition: user condition to match reporter to the email-generated user * Action: edits for your fields... __Bill