Comments
-
@Paka Required few clarifications to understand your use case better * Is it ensured that only 1 user logs time against a unique Vacation issuetype? * if user X has to take 2 days timeoff, will they enter 16 hours total (Day 1 = 8 hours and Day 2 = 8 hours) or will user X create 2 Vacation tasks and enter 8 hours against…
-
2nd JQL condition shows the issues are not matching Done criteria. Looks like all the subtasks are matching not Done criteria. Can you check if there are any sub tasks from above list that were in Done statusCategory?
-
The way i had thought, it is not working :-(.
-
can you share the log of your automation execution
-
@박예담 You can use Trigger as When Issue Linked Branch for Link Issues Use smart value {{issue.issuelinks}} to determine story key that is linked to the task from story determine the parent using lookupissues then edit parent in the task
-
@Mike Ruthven as per documentation, one of the reasons why the fields are not returned is below is it possible that some of the fields are not mapped to any project?
-
@Nur Fatin Have you tried {{issue.url}}
-
This works
-
one of the possible reasons that I can think of is your ABC-123 is getting converted into a hyperlink automatically and hence you are getting 2 values. Can you check that? Also, if your use case requires to check on latest comment then you can use this smart value {{issue.comments.last.body}}
-
if there is only one comment and there is only item matching the pattern, then one value should be returned. Can you share the screenshot of the rule that you have written so far?
-
@Nadege Comments loop over in an array. you should add a condition to break out of the loop when you get first match refer this article and share the screen shot of your automation if you face challenges https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588
-
@David McCann if you want to see say 10 Epics under 1 initiative, you need to update parent field in the epics. that you can do using bulk update feature after searching the issues. In the search screen, on right side you will see ..., click on that and select the option bulk change ...
-
@Elena Bertucco You can create a smart variable say dueDate and set to {{now.withDayOfMonth(15).withmonthOfYear(5)}} When you do edit issue, which ever field you want to set to, use {{dueDate}}. That should work. Also, in your schedule, hope that you are specifying JQL to filter out records
-
@Elena Bertucco can you also share the trigger point for your rule? is your use case is expiry date and due date same? What values would you like to populate for Start date and Completion date in your automation? Currently those are blank as per the screen shot
-
I think what you can do instead of having 3 if condition, in 1st condition, use issuetype in subTaskIssueTypes() and statusCategory = Done then edit issue in 2nd condition, use issuetype in subTaskIssueTypes() and statusCategory != Done then edit issue that will ensure that both ifs are evaluated correctly.
-
@siva.vemula Can you make the change and share the screen shot of what you have done? if you hit an issue, I will be happy to help. However, for your own learning, I encourage you to try this out yourself first
-
in that case in Issue matches JQL use issuetype in subTaskIssueTypes() Then add another if Issue matches JQL condition: check statusCategory = Done then edit issue fields to set Spilled Over = No Then add another if Issue matches JQL condition: check statusCategory != Done edit issue fields to set Spilled Over = Yes
-
@Henning Zobel I doubt it can be done via JQL. Are you open to use REST APIs to get the required data programmatically?
-
@Henning Zobel Your question is not clear. You can use either of the two conditions in the jql. to get list of issues that are tagged to a release which is not closed or has been marked as Released. fixVersion in unreleasedVersions() and statusCategory != Done fixVersion in releasedVersions() and statusCategory != Done if…
-
@siva.vemula You can try below automation rule
-
@Harvindar Singh The columns in boar are defined manually. These don't get mapped to To Do, In Progress, Done categories. When statuses are added in JIRA Workflow, then based on the category defined by end user (Jira Admin), these Worksflow status get mapped to To Do, In Progress, Done categories. The purpose of Boards is…
-
@Harvindar Singh In JIRA SCRUM board, most likely you have not included the required statues in the swimlane, creating the confusion. Can you review and ensure that statuses are mapped properly in the defined columns? Also, JIRA categories all status in three categories - To Do, In Progress, Done depending on how these…
-
@Paul Hobbs Good question. for that you could branch the workflow based on say Teams field or when assignee is in a group or any other custom field. When the condition matches, then only the particular work flow will become visible/active.
-
@Rhonda JIRA Cloud provides free instances for upto 10 users for JIRA and Confluence. Depending on what is your objective, you should be good to start with free version. if you want to manage a To Do kind of task list, have you looked at Trello or similar kanban based tools?
-
@Paul Hobbs Assume you have two workflows named: * Strict Workflow * Relaxed Workflow Next step will be to configure the workflow permissions. For the required transition, add the condition that checks if user belongs to a specific group Finally, assign the workflows to Issue Types. Note: All these steps require JIRA Admin…
-
@Emma Crameri are you on cloud premium subscription? if so one of the options is to use JIRA Plans formerly known as Roadmaps See below link for further details Tutorials for Advanced Roadmaps in Jira | Atlassian
-
This is a great feature and will be very helpful
-
What is the type of jira project that you are using? is it a company managed or team managed?
-
@Mike Ruthven have you run this end point to get the list of fields? https://your-cloud-instance.atlassian.net/rest/api/3/field Once you have identified the fields you should be able to use below endpoint to delete the custom fields url = "https://your-domain.atlassian.net/rest/api/3/field/{id}" Refer link: The Jira Cloud…
-
Can you share the screen shot of what you see when you are clicking on Teams menu?