Trudy P Claspill Community Champion

Here is the link to the REST API documentation https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/

Can you show us the Issue Type Hierarchy configuration page and point out at what level the Milestone issue type has been added? https://YourBaseUrl/secure/PortfolioHierarchy.jspa Concerning the absence in the Advanced Roadmaps Hierarchy list, I believe that shows only the Level Names, not all the individual issues types.…

Hello @Todd Winton Yes, that can be done with Automation. Can you provide a screen image that shows an example parent issue in this case, with the "go live" and "transition team" child issues? I ask so that we can ascertain if those are Subtasks, or child issues under Epics, or if the relationship is created in some other…

No, another condition is not needed. First, the Subtasks are under the Story, and the Story is under the Epic. The Subtasks are not directly "under" or "in" the Epic. Second, this part of the JQL parent={{issue.parent.key}} is used to get a matching subtask under the same Story as the subtask that triggered the rule. The…

Hello Denny, 1. What is the field type of Target Start? Is it a Date picker, or Date/Time picker? 2. Remove .fields from the smart value. It isn't necessary. 3. Add a Log action to just print {{issue.Target Start}} to confirm that a) you have the correct field name and b) It actually has a value. I tested with a Date…

I don't think I clearly understand your requirements, so I will start with this set of requirements. When an issue is transitioned to Complete And that issue is a Sub-task And the Summary of that issue is 18.05 Ready to construct (100%) Then find all sibling subtasks that have the Summary 18.1 MDU Equipment Received And…

Hello @Denny Ransom Welcome to the Atlassian community. Rather than using all that Substring stuff you could use this to extract the numeric Month value from the date field {{issue.Target Start.format("M")}} Referring to the format command described here:…

Let me repeat back what I think you said. Correct me if I make an error. Modifications are bold. When the status of Sub-task 1 changes to Completed And that subtask has a particular value for Summary And that subtask exists under child issues under Epics where the Epic meets certain conditions You want to change the status…

Hello @Corey Hemingway Welcome to the Atlassian community. From a browser tab you can execute the REST API call to retrieve all custom fields. https://YourBaseURL/rest/api/3/field You can search the output for the custom field identifier. That will show the Project IDs for the project(s) that use that field. You can get…

Hello @Emerson Henrique Cavalcante Welcome to the Atlassian community. What would you then expect to be able to do with that information, if you were able to split story points in that manner? You could create Sub-tasks for each task that needs distinct story points. Story Points are not normally estimated at the Sub-task…

Hello @Beatriz Have you tried to create that automation? Trigger: Issue Transitioned Specify destination status Condition: Field Value Condition Issue type equals subtask Action: Clone Issue Specify the destination project and issue type Specify other fields to set, and their values

Let me repeat back what I think you said. Correct me if I make an error. When the status of Sub-task 1 changes to Completed You want to change the status of Sub-task 2, which is under the same Story as Sub-task 1. All Sub-task 1 tasks (under multiple Stories, under multiple Epics) have identical Summaries. You want this…

Hello @Pradheep Ayyanar Are these issues all in one project or in separate projects? How do you identify the issues that need to be changed to In Progress? Are they linked to the subtask? What event do you want to trigger this rule? Would that be the changing of the subtask to Completed?

Adding to this... Jira's native search capabilities do you support imbedding in the query a comparison of two date fields nor a calculation of the difference between date field and criteria for the query. Are you willing to consider a third party app if one could give you the date differencing capability directly in the…

Hello @Christopher Brinson Welcome to the Atlassian community. There is not a native solution available via the UI. It might be possible to create your own custom solution using the Jira REST API.

To create a rule that can access and update issues in multiple projects the rule has to be created as a Multiple Project Scope rule. Those can be created only by Jira Admins. Such rules can be set as Global scope, meaning they can be triggered from every project, or they can be set to specify a subset of projects…

I have two suggestions: 1. Add a Log action to print out the value of the smart value you are trying to use. That will add a message to the rule execution log showing the actual value the rule is trying to insert into the Original Estimate field. 2. Add the Conditions I previously recommended to ensure that the date fields…

In what way is that not working? What value do you actually get in the field? What value do you expect to get in the field? What is the output in the rule execution log when the rule executes?

@Shatakshi Mete For future reference the "Community Contests & Kudos" forum is not really the best place for a question about Atlassian tools. You might want to consider the Jira Discussions forum, one of the Product Group forums, or one of the Industry Group forums.

How is that different from what you saw before?

Hello @Vivianne Juma Welcome to the Atlassian community. What message are you getting when trying to create an account? You have created an Atlassian Cloud user account to access this forum. The same Atlassian account can be granted access to Atlassian Cloud products like Jira.

Admins with appropriate access may access user management from the cog/gear icon on the right side of the menu bar in Jira. Another path is through Organization Administration at https://admin.atlassian.com, and then through Directory, and then Users.

I believe that the problem is in your JQL in the left side where you put the field name you have entered Standup but you have otherwise stated that the field name is StandupFlag. In the JQL you are not comparing two values to each other. You are telling Jira to compare the value you supplied on the right side to the value…

Hello @Hanafi Sapei Welcome to the Atlassian community. Check with the Organization Admin for your Atlassian Cloud, or the Jira Admin. Ask them to check if you and your team members are still granted an Agent license to you JSM product. If you don't have an Agent license then you won't have the Reply To Customer option.

Thank you for that additional information. The best solution is to create a new Field Configuration where the Affects Version field is set to Required. Then create a new Field Configuration Scheme. In that Scheme, make the original Field Configuration the default. Then add your new Field Configuration to the Scheme…

I have not been able to replicate what you are experiencing in my own environment, but changes are not rolled out to all environments globally simultaneously.

Hello @Katia Cypers Welcome to the Atlassian community. Your post seems to be incomplete. Can you provide more information? Can you provide a screen image of what you see currently? Can you describe how it appeared previously that is different from the current presentation?

Hello @Ali Moeen What is the project type for the project whose issue you are trying to move? You can get that information from the Type column on the View All Projects page under the Projects menu. You will have to contact the Project administrator for the project the issues belongs to, and possibly they will have to…

Thank you for that additional information. Looking at your second example of how it previously displayed, it appears that it showed IDs for users who may have been deleted from Atlassian Cloud. In your first example of how it appears now, I see that all those visible are marked as "(deleted user?)". You can check if the…

Hello @Luis Genao Has the issue resolved? Or have your administrators been able to contact Atlassian directly for help?