Bill Sheboy Expert

Hi @Magdalena Migas I do not believe there is a way to disable them with out-of-the-box JIRA. There are several suggestions to add this feature, which you can review and vote for:…

Thanks for the additional information, @Lionel Wolberger How high is the team's WIP and how much throughput do they have? When WIP is low (so less task-switching), one alternative to estimating the actual size would be to review cycle time, look for outliers, and discuss those for learning opportunities. The built-in cycle…

Hi @Christopher Macnichol -- Welcome to the Atlassian community! This sounds like a timing issue with the rule firing. Please review your second rule's details, and check the option to "Allow rule trigger". This will enable the action of the first rule to result in a trigger of the second one. Best regards, Bill

Hi @Evgeniy Nechaiev -- Welcome to the Atlassian community! The assignee field is a specific person (user) of JIRA, not a generic role that multiple people belong to. What problem are you trying to solve? Are you trying to mark the item as available for someone in the "Tester" role to pull for work? If so, perhaps you just…

Hi @raju mandapaka To clarify your request... * Are you trying to get all issues assigned to a specific person, and some of those issues are also linked to other issues? * Are you trying to get all issues assigned to a specific person. And, for each of those issues, get any issues linked to them regardless of the assignee.…

Hi @Tobias Jakob What is the problem you are trying to solve? Why would there be multiple tickets/issues with the same summary? Are they duplicates? Let's say they aren't duplicates, and that both are needed... One way to solve this would be to create an automation rule: * Trigger: summary field changes * Branch: JQL to…

Hi @Lionel Wolberger To confirm my understanding, is your team re-sizing "done" work at the end of sprints in order to measure this delta you are asking about? Thanks, and best regards, Bill

I agree! Seems like some of these went to the "future consideration" chasm. https://jira.atlassian.com/browse/JSWCLOUD-20445 https://codebarrel.atlassian.net/browse/AUT-1968

Thanks, @Alex F for clarifying your request. According to the work Code Barrel did on the item below, this should work. The only difference is for legacy and non-legacy property access. I checked and didn't see any open defects for cloud or automation on this issue. https://codebarrel.atlassian.net/browse/AUT-83 I suggest…

Hi @[deleted] You can set a default value for empty fields with the pipe followed by the default: {{issue.field|mydefault}} Best regards, Bill

Hi @Greg Messemer -- Welcome to the Atlassian community! Were you able to figure out this issue? To export from JIRA, you * Navigate to Issues and Filters * Create a filter for the items of interest, * Select the Export to CSV at the top right of the page, under Export There is a limit of up to 1000 items for exporting. If…

Hi @qais_alkhateeb You were expecting 1 email with 100 issues, and instead got 100 emails. Correct? This can happen if you are using the branch to iterate over the issues rather than the lookup action. Here is an example rule which would do what you ask. * Trigger: probably scheduled once per week, based upon your…

Hi @Luiz Gustavo Gregorio Are you still working on this issue? If so, there are two common reasons for this symptom: either the issues are not marked as resolved correctly or the underlying items or filter have changed. Regarding resolved, check your scrum board's columns, and confirm that the resolution is set when items…

Hi @Vishal There is no way to distribute the dashboard by email with out-of-the-box JIRA. Instead, you can create filters and add subscriptions which send them to people. There are some old requests to add this feature, but they do not look like they are moving fast in the backlog. Take a look, and please vote for them if…

Awesome! I am glad that it helped you. __Bill

Hi @Nofar Ben Kereth Try this to solve the problem: * Trigger is sprint started * Action to Lookup issues, matching JQL for your missing field data. For example: project = {{issue.project}} AND sprint IN openSprints() AND myfield IS EMPTY ORDER BY Key * Action send an email with the list of issues. For example: Here are…

Hi @Franz Maruna I believe you are seeing a few effects... First thing, the execution order of the automation rules is not predictable. So consider the triggers and when things could happen. Next, rules can trigger other rules, but when you want a rule to be triggerable by another (such as transitioning to change status…

Hi @Malka Were you able to figure this one out? I did some checking and I noticed: * The function endsWith does not handle empty values or mismatches well. I got around that by using the default value to support the IF test. For example, IF({{somefield.endsWith("Hello")|false}}, 10, 20) * In your formula, some things…

Hi @sharon flynn -- Welcome to the Atlassian community! In case you haven't solved this yet, have you tried a bulk edit, and a move operation? You could create the new project and then move the issues you want at one time. Please see here for information about bulk edit:…

Hi @Raven You can suggest this as a new feature if you are interested. I just checked and didn't see anything similar to it regarding community postings. Best regards, Bill

Hi @[deleted] Have you tried something like this, then find the ID, and proceed from there: project = myProject AND sprint in futureSprints() ORDER BY sprint, key Best regards, Bill

Hi @Season Hughes What you are asking for is not in out-of-the-box JIRA. If you feel strongly about needing this, consider writing a suggestion to add the feature. I could not find any similar open suggestions for this idea. Also, please consider reviewing some of the explanations and discussions around the purpose and use…

Thanks, Alex. That clarifies what you are trying to do, and I do not think you can do that for a user who is not already a specific actor for an issue/trigger, such as initiator, reporter, etc. Since Atlassian implemented their GDPR changes, access to some of the user information is further restricted. Please see here for…

.

Thanks, @Jakob KN for the follow-up. If you believe this would be a valuable capability, please consider adding it as a suggestion for Atlassian to consider. Thanks!

Hi @James Malgieri Sounds like John was pointing you in a good direction. Once you add the custom fields for your inputs and the score/defined risk level, you can: * Create a new rule: project settings, automation, create rule * Trigger: issue field changes for any of your input fields. You may want to limit this to edit…

Hi @atullio -- Welcome to the Atlassian community! Have you already resolved this? If not, please take a look at your board's filter. It may be concealing the items based upon the status or some other criteria. Best regards, Bill

Hi @Steve Merrick Did you figure this out? I experimented, and when a label no longer has any rules assigned/associated, it vanishes within a second (or the next page refresh). So, it appears delete is auto-magic. :^) Best regards, Bill

Hi @kumargaurav-tudip -- Welcome to the Atlassian community! Did you figure out this issue yet? From the automation rule perspective, I saw the same challenge that a Convert to... action cannot be accurately detected for changing to/from a sub-task as a trigger. I created a defect for this issue for automation triggers.…

Hi @abalantrapu1 Have you already solved this question? If not, have you tried to log into JIRA as the service account and then navigate to the API token generation page? Per Atlassian's support comments on this forum, only an active user can create an API token.…