Dick Community Champion

Let the tester keep track on his notebook and report the number of tests and the fails into two separate numeric custom fields. You can have a third custom field with the percentage passed. that can be filled using math expressions (standard in Jira, no need for plug-ins here).

Sub-tasks should be all done :)

If the approving person wants to know his to-approve items, use a quickfilter on the board to filter issues with reporter = xyz ( or: reporter = currentUser() ) The transition to "Done" can have a restriction of the persons allowed to do the transition by the indicated "only reporter condition". 

https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466322168/Tags+and+Expressions 

try smart values? {{issue.customfield_21011}}

Hi, For part one, the creation of issues 1-7 you can use automation, using {{triggerissue.name}} as the smart value for setting the variable part of the name "ABC". The edits upon transitions you request can be mostly covered using post-functions. The time correction should be done in an automation rule. Closing the epic…

We're running Jira Datacenter 9.4.14 with Automation for Jira 9.1.1. You can find it under the blue action icons:

Hi Oded, What about doing a re-fetch of the issue after your bug-change?

Hi Sara, Some things to respect in your automation (in terms of keeping it simple): * You're not checking if the parent link (a custom field!) is empty prior to requesting parent-stuff. * Project-screening can be done on the rule scope. If you insist in putting it in the automation, please consider putting it as one of the…

Automatic reassignments are in fact post-functions inside the workflow (interface visible when clicking the arrow between statuses when editing the workflow). You can remove these post functions if they don't do what you expect. the ticket should remain on the assignee. Validate the user being the reporter when…

This is especially true when using Plans. For some reason storypoints can only be visualised in a Plan when the issues displayed originate from scrum projects. Any Kanban project issues screw this up (as in: the option to use storypoints in the Plan configuration is greyed out). Hence, it is important to know the original…

@Guy Anela For me, the {{changelog.Epic Link.fromString}} is not filled with the preceding epic link. It prevents me to do calculations for the original epic (prior to changing the issue's epic link). As Atlassian is busy with changes regarding the parent / parent link / epic link, I've tried multiple ways to get this…

Sincere question: What would be your solution when stories/tasks are reallocated to another epic? I figured out your method is applicable for the destination epic, yet how do you recalculate the (also changed) storypoints of the origin epic? Both recalculations would be needed to have an accurate overview.

Older issues can be unwatched using JiraPS (Jira Powershell) commands: Import-Module JiraPSSet-JiraConfigServer 'https://yourJiraInstance'New-JiraSession -Credential $cred Get-JiraIssue -Query 'project = "YourProject" '| Remove-JiraIssueWatcher "YourName"

After the splitting of project A into project A and B and moving appropriate issues to B, we had the same issue as the original poster. In both project A and B we had sprints defined: Sprint 1, Sprint 2 and Sprint 3. We solved it in the following way: In project A, we entered three new sprints named Sprint 1A, Sprint 2A…

Hi Bill, I'm on the Data Center edition of Jira. I certainly hope this feature gets implemented for this as well. The consecutive if/else conditions are non-dynamic, which means extra work if the options of the checkbox change/get new entries. Thanks for the info, nevertheless. Best regards, Dick