Bill Sheboy Expert

Thanks @Tanguy Crusson for the response. I have a couple of other questions regarding licensing and permissions: * Who (i.e. which Jira roles) can add Creators, Contributors, and Stakeholders, or change existing roles for a JPD project? * Where will this happen in the product: in JPD project settings or in the Site Admin,…

Hi @Ryley Fischer Yes, and...to Mikael's answer: If you decide to add the custom field and add an automation rule, you can run this for issues from prior sprints to determine if this is an older symptom or a newer one. For example... * trigger: scheduled (e.g., every hour), with JQL to find issues in your project where the…

Hi @Tanguy Crusson Thanks for this information! Would you please clarify your post above: It works like Jira Software: site administrators do not need Jira Product Discovery product access (a license) to create projects and manage project settings, but they would need a license to work in the projects. Will a Site Admin be…

Yes, that sounds correct. I added a re-fetch after the trigger as a precaution.

Hi @Brian Taylor If you look in the details of the Delete Attachments action, it will point you to a reference for creating a regular expression. I recommend looking there to confirm you have what you need. For example, a very basic one to remove just the *.xlsx files would be this: (.+\.xlsx) Kind regards, Bill

Hi @Mimi Peters I believe you will need to use if/else conditions for each group, as I do not believe there is a rule function as you show for user_is_in_group() Your rule could be like this: * trigger: issue created * action: re-fetch issue (To confirm the data is fully loaded after the create) * if/else condition:* user…

A possible work-around for this is... A recent change allows team-managed projects (TMP) to share/use the custom fields created for the site and company-managed projects (CMP). If you create a multi-select user field at the site level, it could then be used by your TMP (instead of the People field type). That may work…

When creating JQL for use in a rule, it can help to create it stand-alone first using a specific example, in advanced issue search. Then change it to be generic using a smart value. From what you described, you could try this in the rule (substituting in your project name): project = myProjectName AND Parent =…

Hi @Alex Hoogendoorn Have you looked at the sprint report to learn if there were either any scope changes (i.e., issues) or edits to the story points of the issues in the sprint? I ask because I noted in the documentation (under those question mark icons) that the burndown uses what Atlassian calls the "committed" value at…

Hi @Courtney Sexton -- Welcome to the Atlassian Community! A board is a view of a project's issues, based on a filter. Have you checked that your moved issue matches the filter for the new project? If it does not match it will not appear in the backlog or on the board. And, what are the types of source and destination…

Which of the linked information that I provided did not help? No, as I noted you cannot reference the Component details from the issue. Instead please try the work-around that I noted to use the Component id value to call the REST API, obtain the lead information, and use that to add the Watcher.

That is correct: the lookup issues action has a limit of 100 issues.

You will need to divide the estimate value to convert seconds to working days first: 60 seconds/minute x 60 minutes/hour x 8 hours/work day = 28,800 seconds/work day {{issue.customfield_10015.plusBusinessDays(issue.timeoriginalestimate.divide(28800))}}

Hi @Dmitry Babenko -- Welcome to the Atlassian Community! What have you tried thus far to solve this? If you have a rule, please post images of your rule and the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. If you have not started your rule yet...To get…

Hi @Maksim Fin Creating rules to solve problems and automate repeating tasks requires learning and experimentation. It is good practice to first try to create a rule, and then ask for help if you run into challenges. To get you started on creating your rules, please review this documentation and examples: *…

Hi @Graham Wellington -- Welcome to the Atlassian Community! I do not believe that is possible with built-in JQL features; it would require comparing two issue fields in the JQL: the Due Date and the Status Category Change Date (assuming your "Closed" status has a category of "Done"). Your options to solve this may depend…

Hi @Ron Barak It appears you have changed your JQL to substitute ampersands (&) for the AND operator, which is not going to work. I recommend either replacing these manually with %20AND%20 to escape the spaces around the operator, or run your query from advanced issue search, and then grab the well-formed query from the…

Hi @Jamie Bell -- Welcome to the Atlassian Community! Is this for a team-managed or a company-managed project? If it is team-managed, there is a known problem with People fields not working with all dashboard gadgets. You may watch/vote for that defect to see progress: https://jira.atlassian.com/browse/JRACLOUD-72205 Kind…

Hi @Georgi Nikolov Adding to the other answers provided... The Issue Created trigger can happen so quickly that the data is not yet ready for other things, such as conditions and actions, leading to unpredictable results and rule errors. When using the Issue Created trigger, it is a good idea to immediately follow that…

Hi @Vitor Seabra -- Welcome to the Atlassian Community! I believe the Original Estimate is stored as seconds, and so if you divide that value (based on your site settings for work days/hours) into whole days, it can be added to your field with plusBusinessDays() {{issue.yourField.plusBusinessDays(yourIncrementValue)}} Kind…

Hi @Casey Gould Is your custom field a date field or a date/time field? If it is a date field, what I suspect is happening is the values are not comparing as you expect because one (or both) are converting to text for comparison). You could force the behavior you want by either: * using the date diff function and checking…

Hi @Adam Ziecik What about using the JQL (or related issues) condition to find all issues with the same parent, and which are not issueType Test, and which are not done? If there are none, proceed to transition the epic. Generally, if you can write JQL to answer a question, a rule can use that JQL for deciding actions.…

Hi @bmacd You are correct that the "Copy Labels from Epic issue" is a replace, not an add to existing, operation. I recall answering this scenario before, and I'll look around to see if I can find the post/link. The solution is to add the additional labels using advanced edit with JSON, such as: * branch to the epic and…

I was noting that the list function last returns the last item in a list...with no regard to an desired ordering. If the list is in the correct order, you are okay, however...if you needed the the most recent item by date, consider using another method to find that value.

Hi @Naveen Vastare -- Welcome to the Atlassian Community! For a question like this, please post images of your complete rule and the audit log details showing the rule execution. Those may provide more context for the community to offer ideas. That error seems to indicate the message was received and was not authorized for…

Hi @Joey Huang -- Welcome to the Atlassian Community! FYI for older posts like this one: it can help to create a new question and link back to the older threads. Otherwise only the people following this one will see it. Back to your question...Would you please post images of your complete rule and the audit log details…

Have you tried using a Quick Filter with JQL to show what you need?

No, there is no built-in, automatic way to refresh the page after the rule runs. Next, when you reference {{issue.sprint.last}} that is not necessarily the latest sprint, as the order of the sprints within the field could change. Perhaps instead try {{issue.sprint.startDate.max.jiraDate}} to see if that works.

Ah...I missed this is a team-managed project (TMP). I believe you need to set the parent field as TMP do not use the Epic Link. To do that you will need to use Issue Edit with JSON.

I just tried with a team-managed project and the rule triggered correctly for creating either an epic or a child issue from the roadmap. As you are on a paid Jira license, and are a site admin, you could ping the Atlassian Support team to ask why the rule didn't trigger. They may see something in their logging that we are…