Trudy P Claspill Community Champion

Hello @Steve Ruzila Since you said you are new to Jira, I'm going to provide some extra information to help explain this more fully. There are two aspects to specifying the type of a project. One is specifying the type of Jira Product for which the project is created; i.e. Work Management, Software, or Service Management.…

Hola @Juan Gregorio Toro Ramirez , Cuando un usuario se desactiva en Jira Cloud, las tareas que creó permanecen en el producto Jira. Cualquier usuario existente que tuviera acceso a esas tareas seguirá teniendo acceso a esas tareas. No debería ser necesario cambiar los problemas a menos que se haya implementado la…

Hello @PARISATO Marie-Hélène Are the summary and id values you want to use values that you want to configure? Or do you want the field to show a list of issue Summaries and IDs? If the field will be used to select from values that you are configuring, you could use a Lookup Table in your Automation rule to associate the…

Hello @Maxine Freedman-Thompson Do you have any issues that have been resolved in the past 60 days? The chart shows information only for issues that have been resolved in the in the date range you specify.

Hello @Maroline Johnson You could use a Post Function in the workflow transition to the "closed" status to set the Remaining Estimate field to 0. That would handle the change going forward, but would not update the issues that already exist in that status.

Hello @Steve Ruzila Are you working with a Team Managed project or a Company Managed project? If you go to the Projects menu and select View all projects and find your project in the list, its type will be shown in the Type column. Can you provide a screen image of what you see when you navigate to Project Settings >…

Hello @Wendy Benson Thanks for that clarification. I am not aware of a method to display a sum like that in the Advanced Roadmaps Plan. Nor am I aware of a way to show a sum of values from selected issues directly as part of the output of a search/JQL, nor a native Dashboard gadget for doing that. You could use an…

Yes, that is correct. That is stated at the bottom of the screen. You just need to add another field/column to your CSV file to contain a unique number for Issue ID for each sub-task. Just a number; it doesn't have to match an issue key.

Hello @Laure_Tessaro As I mentioned previously, the image you provided where the Epic Link field was blank appeared to be showing that you were trying to fill that field in an issue that itself was an Epic. That is not supported. Please provide a screen image of another type of issue such as the ones shown in the Child…

I apologize. I failed to notice that there is a step missing in your automation rule. You need to set up a For branch to drill into the linked issues to update them. I recommend you structure it like this:

Hello @Scott Federman Please show us the entire rule you constructed and the details of each step.

Hello @Osama Al-Areky I'm glad I could help. If you problem has been satisfactorily addressed by my answer, please consider clicking the Accept answer button.

Hello @Thibaut LEGRAND -HONGQIAO- When we ask to see the Audit Log for an execution of the rule we need to you to click on the Show more link to the right of the entry and show us the details that reveals. {{issue.tasks...}} is not a valid smart value. You can't reference the child issues of an Epic in that manner. When…

As @Craig Nodwell stated, you need to create the custom fields for each of those. The screen you are in is for adding fields that already exist, not for creating new fields. New fields need to be created by an administrator before the can be added to the issue details view.

Please show us the Audit Log for an execution of the rule that does not work, and the details of the Edit Issue action.

I see now that you are trying to use {{triggeringIssue That also is not a valid smart value. As I said in my first response you need to be using {{triggerIssue

Hello @Deema Hendi Welcome to the Atlassian community. The options list will show you only single and multiple select user and group picker fields. Is the More Assignee field one of those types of fields? Is it available in the Field Configuration for the project and not set to Hidden in that configuration?

Hello @Bridget Tracey Welcome to the Atlassian community. What steps exactly did you follow to make the Jira project public? - Has anonymous access been enabled for your Jira site in addition to setting the access/permissions for the project itself to be public? - Are you working with a Team Managed project or a Company…

Hello @David Sheptovitsky Welcome to the Atlassian community. In what way are you not allowed to make changes? Do you not see the pencil icon for opening the page in Edit mode? That could be due to either page restrictions on that specific page or a page higher in the page tree, or it could be due to your permissions for…

Hello @Jael Carvalho Welcome to the Atlassian community. If you want to import subtask and add them to as children under an issue that already exists, then in your CSV file you have to include an entry for each subtask that has the issue key for the parent task to which you want to add the imported subtask. Example:…

What is happening to an issue when it is rejected? Is that another type of status change? TRIGGER: Issue Created CONDITION: Issue Fields Condition Field: Approval Condition: is not equal to Value: EMPTY CONDITION: If/Else IF: Advanced Compare First value: {{triggerIssue.reporter}} Condition: equals Second value:…

Hello @Rajesh Ale You can use an Automation Rule with an Issue Created trigger and a Send Web Request action to execute a web request to add a user to a group (assuming a REST API end point exists for that operation). You can use an Automation Rule Schedule trigger to execute a rule periodically. The Schedule trigger can…

Hello @Wendy Benson Welcome to the Atlassian community. It does not appear that the Roll-up option in the View Settings for an Advanced Roadmap plan will roll up a custom field. You could use Automation Rules to automate updating the field in parent issues as it changes in child issues. If the data is stored in the…

Hello @Nicholas Tsiroyiannis What I would recommend instead is using two Lookup Issue actions and two variables. In the first Lookup Issues action change the JQL to look for only the issues that have overallStatus set to X. Create a variable called overallStatusXCount and set it to {{lookupIssues.size|0}} In the second…

Hello @Michael Zimmermann If the values are added when the issue is being created there would not be any separate history entry for that. For the one issue you have shown, since there is no history showing the field change that suggests it was added when the issue was created. If you delete a value from the Labels field,…

Hello @Gladys.Fernandez Welcome to the Atlassian community. Can you describe your requirement with more details? Try walking us through the scenario - When you take action 1 and conditions 2 and 3 and met then you want the result to be 4.

To be clear that method uses the generic issue linking functionality. That method does not correspond to the built in recognition of parent/child relationships in Jira. Linking issues in that manner will not show them related as parent and children in the Advanced Roadmap Plans functionality available in the Premium…

I was just going to add a note about that, having seen your comment about this defect on other posts. :-) Thanks, @Bill Sheboy 

Hallo @Nils Hornitschek , Willkommen in der Atlassian-Community. Arbeiten Sie mit einem Team-verwalteten Projekt oder einem unternehmensverwalteten Projekt? Diese Informationen werden am unteren Rand des Panels auf der linken Seite angezeigt, wenn Sie auf die Tafel schauen. Beide Arten von Projekten unterstützen das, was…

Hello @Thibaut LEGRAND -HONGQIAO- Can you show us the automation you used to sum up the data from subtasks to parent tasks? With a few changes, the same type of rule should be able to be used for summing from those tasks to their parent Epic.