Fazila Ashraf Community Champion

Sorry, I originally mis-read your webhook as web request :( For the example in question, there doesnt have to be a receiving webhook automation rule. A automation rule that sends uses the 'Send web request' should use the rest end…

Hi @Audio Visual Architects You can't modify the create new project options in jira to enhance like that. But you could trigger a custom automation to create multiple tickets there or do a csv import soon after every new project creation.

Hi @Samantha Slagle Yes it is possible.. Looks like you already sorted out the solution. In which part do you have questions?

@nagpo91 , By adding an issue to a sprint, the sprint value of the ticket is updated and that is an edit operation :) 

Hi @shravya chinthapatla Is it that during transition you want different tabs of the same screen to show based on the status? AFAIK, it is not possible :( You could copy this screen to individual screens and remove the not needed tabs and then map the correct tab screen to the transition.

Ah got it.. Thanks! Unfortunately that section supports only the text based fields :( If you choose the confluence option, it is flexible to include other type fields available in the project..

Hello Tony Could you explain (may be with a screenshot) of the 'formatting options' section where you want it to be displayed?

Hi @Jörg Steinhauer Can you share the email confirmation message that says that this automation fails due to field lock? Locked field would mean that the configurations of the field cannot be changed but the field itself should be editable. I am surprised that the automation says that field cannot be edited due to the…

hmm.. If the rule is not triggered, could you look at the trigger condition? was there any changes there? Is the jql valid? try it as a manual trigger and validate?

sure, here is an example of using additional fields via json

Ah ok.. Like it says there, not all fields are supported. Try using the advanced section with json as input 

Hi @Abhi Not possible with out plugins :( See https://confluence.atlassian.com/jira/how-to-add-comments-to-excel-export-316113321.html 

In your edit issue action screenshot, you are using "Story points" . Update that to "Story point estimate" and that should fix the error :) 

Hi @Jörg Steinhauer By chance does your project have 2 fields "Story points" and "Story point estimation" that is causing a confusion? The automation is editing the story points field and the story point estimation field

Can you re-confirm that you are observing that behaviour? I recently used the automation in my cloud instance to set the resolution and it also set the resolutiondate as current date.

ah.. you are using it in json. You can directly add the field 'Total Processing Time' in the edit action and in the text box give {{#=}}{{issue.KenTest SLA}} / 3600000{{/}} Like :

Hi @Tim Shirazi Welcome to community! SLA of JSM works only in the JSM project tickets. You can create multiple SLAs in the JSM project for each status changes. You could create a board that views these JSM tickets but the SLA feature is not available for Jira software tickets.

Hi @Ken Loh You can use the math expressions . See https://confluence.atlassian.com/automation/jira-smart-values-math-expressions-993924866.html 

Hi @Nikhila Patel Welcome to community! Do you have scriptrunner plugin purchased and installed? Refer to https://docs.adaptavist.com/sr4js/latest/features/behaviours and check whether you are looking at the right places

Hi @[deleted] Yes, it is already feasible. See https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-fields/#Category 

Hi @Ken Loh Through an automation , you could find the diff between these dates and log them. Also refer to the answer in https://community.atlassian.com/t5/Jira-Software-questions/How-can-I-list-the-difference-between-the-created-date-and/qaq-p/1874959 

For Free plans, the support is through community. I am not able to reproduce the problem. May be you could write to the app vendor to check if they have seen such problem before - https://marketplace.atlassian.com/apps/1220574/hierarchy-for-jira-custom-issue-structure-jira-tree-view?tab=support&hosting=cloud 

Interesting.. I just installed the app and uninstalled after playing around with it. It uninstalled properly and i dont have it in my project/apps anymore. As you mentioned that this is for a free plan and Atlassian support can not look into this, could you write to the app vendor about this?

Can you share the screenshot of the 'Manage apps' section? Any app installed should be available there for uninstalling.. https://confluence.atlassian.com/servicedeskcloud/managing-apps-1097175863.html#Managingapps-TheUniversalPluginManager 

Hi @askirelis You should be able to uninstall it from the 'Manage apps' section.

Ah no. In the automation scope of projects, there is no option to configure 'exclude' these projects only.

Hi @Shari Fitz-Patrick You can start the execution with a condition to check for this label and proceed with the actual steps? If all the issues in these projects has to be ignored, you can validate the project as condition and then proceed with the steps.

@Jeffrey Bistrong , you have to look through the project roles in your project and see which one can have this account. By default, the automation rule actor is in the atlassian-addons-project-access role. Referring to https://support.atlassian.com/cloud-automation/docs/transition-an-issue-with-automation/ 

Hi @Jeffrey Bistrong You could use the jira.permission.edit.applicationRole property and restrict it to a role where the automation execution account is part of? Refer more in https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/

Hi @Patricia DeLuca You could have an automation to send email https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Send-email to the managers based on certain criteria identified in the ticket.