Trudy P Claspill Community Champion

Hello @Margots Kapacs The document you referenced applies only to self-hosted Jira. According to the tags on you post and the URL you showed in the image you posted you are using Jira Cloud, not self-hosted Jira. This is the correct document for Jira Cloud Auotmation Service Limits:…

Please use a Log action to print the value of your variable in the Audit Log. If TK111111-6 is the issue that is triggering the rule, and If you are setting the variable to {{issue.key.substringBefore("-")}}, then The variable is getting set to TK111111, and TK111111 is not a valid value in the selection list for which you…

Hello @Rohit More , Please provide more information. The above guidance is the steps necessary to achieve the requirement you described. What additional information do you need? Where are you stuck trying to implement this?

Please review the guidance and example. The Condition needs to be directly after the trigger so that the rule will stop before trying to edit a subtask.

Hello @danielnette75 Welcome to the Atlassian community. A Jira application can generate such a message when somebody uses the feature to "mention" you in a Jira issue. The issue ID in this case is AR2D-1. It could be legitimate or it may be a phishing scam. It is hard to tell with having the full content of the email…

Hello @sofiagonzaloc Welcome to the Atlassian community! There is still no self service method to remove oneself from Atlassian Cloud products. Only the administrators of those products can remove you.

Olá @Airton custodio dos santos , Bem-vindo à comunidade Atlassian! Esta é uma comunidade de usuários de produtos da Atlassian. Se você gostaria de nos fazer uma pergunta sobre os produtos, você pode encontrar fóruns para cada produto onde você pode postar perguntas. Clique na opção Produtos na barra de menu na parte…

Hello @Pritpal Singh You can get the Original Estimate and Time Spent information per issue in the output of the Advanced Issue Search screen. If you change the view from Details to List, you can then add the two fields to the Columns displayed in the output. You would use the filter of your choice for selecting issues.…

See @Bill Sheboy answer. :)

Yes, this! I was just about to add to my own answer that I used an Advanced Compare rather than a Condition with JQL.

So the answer may lie in grouped labels? I'm not sure what you mean by "grouped labels".

I am stumped. I have not been able to recreate your issue yet, but I am using Jira Cloud rather than Jira Server/Data Center. If your instance is still covered by a support contract, I suggest raising the issue with your Jira Admins and requesting that they open a support case with Atlassian Support.

I think you've got it! Let us know if you have additional questions.

This works for me. I used the Assignee field for testing. Step 1: Step 2: Step 3: Step 4:

Adding to this, I recommend that you add a Condition after the Trigger so that the rule will not continue processing when the created issue is a subtask or an epic.

Hello @Leena Siddamshetty Setting a default value for a field does not result in the value being set for issues that already exist. The default value is applied only through the Create Issue screen.

Hello @Simon Shim Welcome to the Atlassian community! Does your Epic have its start/end date fields set explicitly? Or are you wanting those to be inferred from the child issues? If the latter, have you enabled the Roll-up Dates setting?

Hello @Lindsey Arwine Welcome to the Atlassian community. How are you recording the estimated story points for the Epic? Are you setting that directly in the Epic? Are you calculating the value based on summing up the story points in child issues? How would you determine the number of story points completed? Would that be…

This works for me. { "fields": { "Story point estimate": null } }

Hello @Gergana.Damyanova Is the custom field one where you can select only one value or were you can select multiple values? Have you confirmed that the smart value {{issueProject}} actual contains MC by using the Log action to print the smart value in the rule Audit Log?

Unfortunately, if @Rede Paulo de Tarso is truly using a Free version of the product as the post tags indicate, then it is not possible to add users to project roles and thereby utilize a Permission Scheme that grants access based on Project Roles. It also is not possible to customize the Permissions Scheme. Refer…

An alternative solution, since you are not currently using the board sub-filter, would be to reset the Hide Done option to "Never" and add a sub-filter to your board as follows: That will result is the board showing all issues (within scope of the primary board filter) that are unresolved, and those that have been resolved…

FYI - Having the "Hide Done" option using the Resolved field rather than the Updated field is a change request documented here: https://jira.atlassian.com/browse/JSWCLOUD-21897

To effectively apply a filter to a single column you would have to construct it thus: <your filter for the column> OR <a filter that selects all the issues that would appear in other columns> There is no way to indicate a Quick Filter should be applied to only a specified column.

Hello @Carlina Bliss If the issues already exist and you want to make existing issues children of other issues in the extended hierarchy, edit the "Parent Link" field to specify the issue that you want to become the parent of an issue. For example, these Epics have no parent currently. I can go to the details page for…

Hello @Jim You said specifically "Story point estimate". Does that mean that you are working with issues in a Team Managed project? Can you show us the Automation Rule you are currently using to set the value to 0? In my system "Story point estimate" is not a field that is selectable in the field list in the Edit Issue…

Hello @Golnoush Taghizadeh Welcome to the Atlassian community. I tried to create "Message Custom Field (for view)" this time and it showed-up on our create issue screen, but default value is empty, no matter what we add as default value. Based on the description for the field, this is correct functionality. It says the…

Hello @Jamie VanderZouwen There is no simple, one-step native solution for this. Are you working with issues in a Company Managed project or a Team Managed project? And when you are counting how many issues are in a status, is that for all issue types in a given project, for a subset of issue types, and/or across multiple…

I think you would need to use an alternate multi-select field to designate multiple teams' involvement in a particular issue. That could be Components, Labels, or another custom field. Unfortunately that alternate field would not directly use the Team values so you could end up with a disconnect between the Team…

Is the field available on the Edit screen for those types of issues? Does your selection of issues include just one project, or only projects where the field is available on the Edit screen?