Trudy P Claspill Community Champion

@Brandon Fish The functionality was changed months ago for the Epics panel to rely on the Status Category of the Status field of the Epic. If that Status of the Epic was green (making it a Status within the "Done" Status Category) that would remove the Epic from the panel. That is the Status field you see above the Details…

Hello @Jessica Oveys Welcome to the Atlassian community. I see it also in my Free instance. There is a bug opened today on this issue. https://jira.atlassian.com/browse/JSWCLOUD-27027 You can click the "This affects my team" option and Watch the issue for updates.

Hello @Nacho Cortes @madhu_sharma @Charles Kato Welcome to the Atlassian community for the new folks. There is at least one other post reporting the same problem. https://community.atlassian.com/t5/Jira-questions/Epic-panel-displaying-too-many-epics/qaq-p/2779813 And I see it also in my Free instance. I found a bug was…

Based on the output the rule is saying no linked issues exist. Since both rules are triggered by "Issue Created" it is a good bet that using the Delay action will resolve the issue.

Hello @Susan Merola Welcome to the Atlassian community. Thank you for providing the screen image. Can you also provide the details from the Audit Log for the execution of the rule? How are the linked issues getting created? Is that done during a separate automation rule? I don't see any steps in this rule to create and…

Hello @Adrian Szubert You could use an Automation Rule to detect that the field has been changed. In the rule you would then check the current status of the issue. If it is not in Status B you could use the rule to revert the field to its former value. Using the Field Value Changed trigger gives you access to a special…

That is unclear. Various people have asked Atlassian directly about that over the past few months, and gotten various answers. See https://community.atlassian.com/t5/Jira-questions/CSV-Import-Roll-out-to-come/qaq-p/2637395 I have not seen any truly clear documentation. If you look in the latest weekly update post all…

Hello Ken, In your example each Epic had only one Customer and only one agent. Will that always be true, or might you need to associate multiple customers and/or multiple agents to a single Epic? Would you want people to be able to enter new customer and agent data, or restrict them to selecting from predefined lists?

Hello @Kentaro Iijima Welcome to the Atlassian community. Is the customer data stored in another system/database that you want Jira to access? Will there be only one customer to associate with each Epic? How will you know which customer should be associated with each Epic? Are you anticipating a need to get reports of…

Hello @William Bolling Welcome to the Atlassian community. It seems like you think you are communicating with somebody specific with your statement "If you need me to run it through Vince..." You have posted your question in a public user forum for users of the Jira Service Management product from Atlassian. We are not…

Hello @Yong Wei Kee A new import process is being rolled out. Try going to settings > System > External System Import.

Hello @David Redman Welcome to the Atlassian community. Your question is posted in the Automation Questions forum. Does this have anything to do with Automation? If not, I can move it to the Jira Questions forum. Are you working with Jira Cloud or Jira Server/Data Center? Can you show us the configuration you entered for…

Hello @Mika Lahtinen Welcome to the Atlassian community. The short answer is "no". The Timeline feature available when you are viewing a project/board is a basic feature that does not offer much customization. For more customization options you have to use Plans.

Hello @Darren Bauer Regarding linking Jira Cloud to Bamboo, a Google search for jira cloud bamboo integration brought up this as the second result: https://confluence.atlassian.com/bamkb/linking-jira-cloud-with-self-hosted-bamboo-389284242.html Additionally the documentation on Application Tunnels says that method is…

Hello @Kim Vencill Welcome to the Atlassian community. One way to solve this is to replace what you have here: ...with a branch to Most Recently Created Issue: I notice though that you have another branch already - a Smart Value branch. Branches can execute in parallel, so your branch to update the most recently created…

Hello @ThePokyWizard You could do that with an Automation Rule. https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/ The basic structure would be: Trigger: Issue Assigned Action: Edit Issue Field to Set: Due Date Value {{now.plusDays(X).jiraDate}} However, how do you decide and annotate the number of…

I just realized though that John's suggested JQL misses part of your requirement - Active, as in not in a 'resolved' or 'transferred/rejected' status at that date or after it. To adjust for that, use this query. project = ABC and status was in (Investigation, "Development Required", "Awaiting GA Release") on…

-Are Resolved and "Transferred/Rejected" actual Status values or Resolution values? Resolution values As per your diagram those are Status. Jira does not have a native reporting option that would enable you to run one query and get the information parsed out for each of the past months. The suggestion made by @John…

You are welcome! Since my responses helped you solve your issue, please consider clicking on the Accept Answer button above my initial response.

Hello Rania, Please be clear that an Automation Rule (global or project specific) cannot prevent a transition from happening. That can only be done through the workflow associated with the project. For a Team Managed project the workflow configuration options are not as extensive as for Company Managed projects. Refer to…

Hello @Rania Haddadin Automation rules cannot be used to prevent an action from happening. Automation rules are triggered by completion of an action. An Automation Rule could only react after the transition has completed. Instead you need to modify the workflow transition to the "done" status to add a Validator to confirm…

I recommended you use the Log action to confirm who the rule is seeing as the Initiator of the rule. Alternately, simply change the Actor of the rule to Automation for Jira. I believe the problem is that you have the Actor set to Initiator, and the actions and conditions in your rule can only be executed by a user that has…

Hello @Rachel Gornall Can you provide some example data to illustrate would should and should not be included in the results? If an issue was active on Jan. 1 and still met the criteria on Feb. 1 should it be counted in both months? Does it matter when the issue was created? Are Resolved and "Transferred/Rejected" actual…

Hello @Jeffery Mangold Welcome to the Atlassian community. Can you share with us the final combined query that is not getting what you want? The problem could be related to your parentheses, but we need to see the actual query to determine if that is the case. You can simplify your first query by using the IN operator with…

@a855031 I notice that you marked @Nicolas Grossi 's answer as Accepted. If @Bill Sheboy 's and my response helped you resolve your requirement, please consider clicking on the Accept Answer button directly above Bill's first response also.

Hello @Adrian Szubert I notice you clicked the Accept Answer button on your own Answer. Did you get all the information you needed to resolve your requirement? If my and Bill's responses helped you solve your requirement and you have no additional questions, please consider clicking the Accept Answer button on our answer…

@John Funk I actually have not found a way to do that myself in either the Free or Enterprise instances to which I have access, and I haven't found any documentation about disabling it either.

Hello @sreenivasulu gundagula Welcome to the Atlassian community. Conditional display of fields based on other fields is not something that can be managed with Automation Rules. For that you need a third party app. One app that might help you, depending on other factors of your scenario, is Behaviours for ScriptRunner.…

If my responses have helped you solve your requirement please consider clicking the Accept Answer button to mark your post as Solved.

@John Funk The user has the bulk change permission based on the first line in the pop up. The error message is displaying where the option to switch to the new issue search experience should display. The content of the message also indicates that switching to that experience has somehow been disabled by Jira Admins.