Bill Sheboy Expert

Thanks @Kristen Roth When discussing priority and sequencing, I find it helps to practice methods which are: * simple * low cost * repeatable * team-owned * explainable to stakeholders For an example from Kanban, try classes of service with work in progress limits. Kind regards, Bill

Katie, I believe what is happening based on what you describe is the rule is getting confused by what "parent" is when you try to create the sub-tasks. Focusing on just what you are trying to achieve, I have seen this solved with 1 or 2 rules. Here is the 1-rule way. * trigger: issue created * condition: issue type is epic…

Hi @Katie Schneider Would you please post an image of your rule and of the audit log showing details of the execution showing this error? That may provide more context for the community to offer ideas. Thanks! Until then...some cases where that error can be shown when a field not relevant for an issue type, is not…

Hi @Jason Yeung First thing, JQL is not a SQL, and so it has no aggregate operations like COUNT. With an automation rule, you can use the Lookup Issues action to gather the issues with your JQL, and then check count with the list size: {{lookupIssues.size|0}} Please note: automation rules can only handle up to 100 issues…

Thanks for clarifying! I missed that you were doing server to cloud migrations. Several have found the information below (and included links) helpful. Your current admins could look for features which they use to today to see what is supported (or changed) in cloud.…

Hi @aagrawal -- Welcome to the Atlassian Community! In the future, I recommend adding a new question and adding a link to this related post. That will get the most people looking at it to offer help. Thanks! Are you using Jira Cloud or the Server/Data Center version? Only Jira Cloud supports Lookup Issues, and you may only…

Thanks, John! I repeated my test with custom date/time fields, including setting one of them to {{now}} immediately before the test. After repeated trials I found that the custom field *never* was set to the seconds value: it always truncated (or perhaps rounded. With a seconds-delta no value is noted.…

Hi @Sean Wood I believe if you sketch out your algorithm, you can do this with the built-in date/time functions. Perhaps something like this: * if created date/time's time value <= 0900 then* calculate the difference between now and 2 days from created at 0900…

Hi @Marco Baldelli When I just tried a diff().prettyPrint I got... Field diff test: {{issue.created.diff(issue.updated).prettyPrint}} Field diff test: 288 days 17 hours 59 minutes 4 seconds So...I am seeing the seconds and I wonder where the punctuation you are observing comes from. Kind regards, Bill

Hi @Kevin McGillicuddy and @John Funk Yes, I agree with John. Please try this: * after the trigger, add an action for Lookup Issues with the same JQL you plan to use in the branch * next, add an advanced compare condition to halt processing if no issues are found* first value: {{lookupIssues.size|0}} * condition: greater…

Hi @Andrey Rudnev -- Welcome to the Atlassian Community! Whatever rule you use to transition the epic to "done", you may want to also change the "Epic Status" to "done". We do that so the epics are removed from dropdown lists and the epic panel. To do this, you will need to use advanced edit for the field: { "fields": {…

Hi @Tijs Tijert Adding to Lisa's suggestion: The automation rule's Owner defaults to the person/user in Jira who created the rule. I have not seen anyone assign that to the automation user before. The value of having this be a person is that when something goes wrong with the rule, the automation engine will email that…

Hi @Megha P Yes, I believe it is possible to implement what you describe with an automation rule. I suggest you take a look a the automation documentation and examples, try to create the rule, and if you run into problems post an image of your rule and what you believe is not working. Then the community can offer ideas to…

Hi @Drew Glicker -- Welcome to the Atlassian Community! Interesting...the only way I have seen that done is using marketplace gadgets to show the board and charts on a dashboard. Although the issues on the "board" gadget were not movable. And I suspect one could custom build such a page using information from the REST API…

Mark, you should be able to extract that date using the right() function: https://confluence.atlassian.com/automation/text-functions-993924863.html#Textfunctions-rightright(intlength) For example with your summary layout: {{issue.summary.right(10).toDate}} The rest of the rule would be something like: * trigger: issue…

Sorry to hear that! A work-around would be to use multiple lookups and more JQL criteria and add up the results. For example, count the "In Review", "For Approval", and "Resolved" separately into created variables and then sum up the results. If that still won't work, the other approach is to add counting fields to the…

That is curious, Isabella. If you take that JQL and run it stand-alone for an example Epic, do you get what you expect: "Epic Link" = ABC-123 AND status = Done And...I see another possible thing in your audit log: at least one of those lookup issues calls is finding more than 100 issues, and that is the limit it can return.

Gotcha... Inside of Jira, you would have different options, depending on your project type: company-managed or team-managed. For example in company-managed, you could use something to distinguish teams (like components) and use separate boards and sprints for one project. I am not familiar with iTrack, so I am unable to…

That match() function will return any matches found for the regular expression. If any of them are found, the result "does not equal" empty...so proceed with processing. I tested this way and it seems to work. I believe another way to do this is invert it, and put a regular expression in the second value and try for a…

Hi @Jack Brickey How about an advanced compare condition using a regular expression? * first value: {{issue.comments.last.body.match("(foo|bar|hello)")}} * condition: does not equal * second value: leave it empty You will need to refine that expression if you want whole words only, case-sensitive, etc. Kind regards, Bill

Hi @Jeremy Dickens -- Welcome to the Atlassian Community! For a question like this, you may want to work with your site admin to contact the vendor's support team at iTrack for help. Kind regards, Bill

Hi @Lucas Molenaar Yes, and...to what Jack suggests: How often do you need to perform this query? If you need it once, you could brute force it, by adding a clause to exclude all of the other options: ... AND platform NOT IN (option1, option2, ...) Or, export to a spreadsheet to prune the list by option count. If you…

Hi @Ali Azzam Please take a look at this REST API method for searching using JQL: https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/#api/2/search-search https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/#searching-for-issues-examples Kind regards, Bill

Hi @Sandor Banyai What do your Kanban board's filter and sub-filter (in board settings) look like? I wonder if those issues are somehow being excluded for another reason. For example, the sub-tasks are not visible and so their parent story goes to the "other" swim lane. Kind regards, Bill

Hi @Mark Korolik Yes, and...to what Trudy suggests: I recommend adjusting the Kanban board sub-filter for this need, perhaps adding the resolution date if you do not want to use versions. If you instead change the main board's filter to solve this, those issues will be removed from any of the built-in reports that you may…

Hi @Ganesh Kumar Vary Yes, and...to what Nic notes: When teams build/buy something to solve what should be a short-term symptom (e.g. carrying over work to the next sprint) rather than discuss and experiment to improve the situation, that can make the symptom into "our new normal". And so the team no longer feels a need to…

Hi @Dave F I agree there could be more terse and focused feature comparison documentation from our vendor, Atlassian. With an internet search I expect you can find third-party consultants who have created such comparisons. I am just a customer, so I sometimes resort to such searches to find answers when documentation is…

Hi @Gregory Santoro Team-managed projects (formerly called nextgen) use Parent rather than Epic Link to associate issues to an epic. Please try this JQL project = myProject AND parent = myEpicKey Kind regards, Bill

Hi @kellie.mingus I believe another way to solve the Jira project/permissions constraints may be described in how your team works: * when a shared service team does work on behalf of other client teams, that request belongs to the shared service team... * the shared service team probably has some form of intake, to help…

Hi @Brianna Graf -- Welcome to the Atlassian Community! That is not possible with out-of-the-box Jira, and here is the open suggestion from 2006 to add it: https://jira.atlassian.com/browse/JRACLOUD-9180 Kind regards, Bill