Bill Sheboy Expert

Hi @Andrew Syme I wonder if there is some type of context issue and the current issue is not the one you think it is, perhaps leading to NULL in the field. Would you please post an image of your complete rule? That may provide some context for what is happening. Thanks! Kind regards, Bill

Hi @Jack Brickey Was that the correct link you posted? It seems that addon allows a Jira Team Dashboard to add a OneDrive link, not to publish Jira content (like dashboards) to SharePoint storage. Thanks and best regards, Bill

Hi @Tehmina Aslam Beyond the scope of your question about cascading the epic information (which Nic has answered), I note a few things in your automation rule to consider: * Given the inconsistencies in capitalization/spacing of smart values, I highly encourage you to never use a created variable name that can match an…

Ah...yes, you do. The "Allow rule trigger" option does that. The default is disabled to prevent a runaway rule/looping condition, and in your case you want one rule to trigger another. Sorry I missed that!

Hi @Andrew Grossman From your question description, I wonder: did you try to remove the set of Linked Issues field to confirm that is the cause, and not an error message...well, error? I took a quick look and could not find this symptom on any open bugs in the Jira Cloud, Automation, or Code Barrel backlogs. Next things to…

Hi @Akwo Akwo Do you have automation for Jira installed on your instance? If so, you could create a rule triggered on Sprint Started to set the field. Please check with your site admin to learn if the addon is installed. To learn more about automation rules, please take a look at these sources and examples: *…

Yes, I wish the gadgets were "smarter" that way...but simple typos could lead to lots of values not merging as a single reporting value. The only work-arounds I know of for this would be to use Components, Labels, or a single-select custom field for customer name. Those would allow selection for what you noted.

Greetings, and welcome to the Atlassian Community! Are you using Jira Server/Data Center or Jira Cloud? It appears you tagged this question with "Server". If so, for automation you can only do this with a series of if/else conditions at this time. There is a feature of Jira Cloud's automation for advanced branching based…

Hi @Ashley Godbold -- Welcome to the Atlassian Community! I do not believe you can do that. This is a UI difference between the Company-managed and Team-managed project views. I checked and did not find any open suggestions to add this feature in the public backlog. Kind regards, Bill

Hi @Matthias Pottmeier -- Welcome to the Atlassian Community! As this symptom is specifically for that addon product, I recommend contacting the vendor's support team directly. You can find their contact information on this marketplace page:…

Hi @Sneha Prakash Somnathe If that plug-in is from the Jira Marketplace, I recommend going to the vendor's product page and reviewing their documentation to learn more about it. https://marketplace.atlassian.com/search?query=Sprint%20Capacity%20Planning There appear to be several with similar names listed and so I…

Hi @Olivia Berggren -- Welcome to the Atlassian Community! A Jira JQL search can only query the data in the fields you have for issues. Is the "Verified by" information you note a custom field in your bugs? Kind regards, Bill

Hi @Jordyn K_ Lee Are you trying to filter by the custom field or to chart the values in the custom field? If just filter the values with JQL, have you tried the Jira Two Dimensional chart on your Confluence page? This would be a table allowing you to select rows/columns, such as Assignee and Status. Kind regards, Bill

Thanks for that info, Paul. According to the audit log, the rule seems to be triggering for only one project: FSO. Were there other issues for that same project which did not trigger the rule? And, are these Company-managed or Team-managed projects? I ask because the "Done" status for company-managed project is probably a…

Oops...my bad. Thanks, Trudy and Scott! Here is a suggestion to add that option for Scrum boards also: https://jira.atlassian.com/browse/JSWCLOUD-22865

Hi @federica.niero I see you solved this with a Re-fetch action...which is a common need when using the Issue Created trigger as the event could fire before all of the data is available for use by the rule. I recommend moving your Re-fetch immediately after the trigger, before any conditions. To find the project type, open…

Hi @Scott Grossman Jumping in to try to help here: earlier Trudy noted the setting for the Epics Panel in the backlog view. When a team want to see the Epics listed with work in the backlog, you may disable the Epics Panel. You may find that setting in ... > Board Settings > Columns Kind regards, Bill

Thanks, Daryl. I do not see this symptom listed as a defect in the public backlog, so at this point I suggest two next steps: * Work with your Jira Admin to create a test project and try to recreate the symptom. This will determine if there is something specific with this project or with all the projects. (I suspect it is…

Hi @Daryl Francis Yes, and...to Trudy's ideas: If you look at a specific issue's history/activity, does it show anything else changing the assignee, perhaps another addon app? Kind regards, Bill

Hi! Perhaps check if the ticket was already escalated and then do not move it to "waiting for support" for that case. I suggest mapping out your flow and that may help find how to handle the different edge cases in the rule.

Hi @Alex Tang -- Welcome to the Atlassian Community! What do you mean by the "sprint view"? If you wanted to drop the subtasks from the board, backlog, and reports, try adding this to your board filter: AND issueType NOT IN subTaskIssueTypes() If you want to toggle this on/off as needed, you could instead add a quick…

Hi, Paul. When you note it only worked on 2 issues out of 20, what are you observing happening? Can you post images of the audit log details showing executions where it worked and did not work as expected? Next, I notice you have set this up as a global scope rule. * Is that intentional or do you just need this for one…

Hi @Charles Bovalis Short answer: no, that is not possible. Longer answer: JQL is not a SQL, and so does not have most basic features of a SQL. Depending upon why/how you need the first 3 (or first N), you could create a dashboard with a issue filter gadget and try to limit the results or investigate marketplace addons for…

Hi @Douglas Oliveira Is this the same question you are asking in this other thread: https://community.atlassian.com/t5/Jira-Software-questions/Re-Average-calculation/qaq-p/1983352/comment-id/190406#M190406 Kind regards, Bill

Your JQL in the branch is trying to match on Epic Name and you want to use key in order to get the epic: issueType = Epic AND key = {{issue.parent.Epic Link}}

It appears you are performing that lookup issues inside of the branch on the parent Epic, and so when it references {{issue.parent.Epic Link}} I do not understand what that could be referencing...and apparently neither does the rule. That would be something like: for the Epic > parent > Epic. Which is probably not what you…

Hi @Guy LaRochelle -- Welcome to the Atlassian Community. Please take a look at the third paragraph of my response for an answer: JQL can find issues which have a non-empty sprint value and which were assigned, but cannot easily determine when they were assigned to the person relative to the sprint(s)...or even the number…

Hey, Darryl. I would not recommend brute-force scraping this, as the rules UX appears to be evolving. (e.g. It appears an attempt is being made to solve the rules list performance issues with pagination. At least it doesn't hang any longer when I open my test project's rules :^) Where did you find documentation on that…

First thing: if the rule is not triggering when the branch is created there is something to fix in the connection between the source control tool and Jira. Please investigate that first, and once the trigger is working we can improve the other rule details. Thanks!

Hi, Jeff. I would add to that definition... * The average cycle time...during that period * based upon my filters selected for this report (status values and quick filters), * based upon the most recent workflow definition for the issues shown, and * based upon my Jira site definitions for working days and hours. Regarding…