How the "Issue Workflow" action work?
...
Repeating Issues add-on allows to select one of this three transitions: 'start progress', 'close' or 'reopen' when set-up 'Issue Workflow' repeats. Choosing 'reopen' for 'Issue Workflow' action means the action will be executed successfully at selected date only if the issue will be in CLOSED status. It is not possible to 'reopen' issue if the issue has IN PROGRESS status because there is no such transition in simple workflow. Remember that also any other transition conditions must be satisfied if the 'reopen' transition has them configured in workflow definition.
...
How to set time when the repeating action is being executed automatically?
Versions >= 0.3.0
Just set the time in "Starts on" field. The repeating issue will execute automaticaly at defined time (from field 'Starts on") and with given recurrence rule.
...
| No Format |
|---|
2016-06-10 17:17:00,045 atlassian-scheduler-quartz1.local_Worker-1 ERROR user@domain.com [jira.issue.clone.IssueCloningService] Could not clone issue TEST-408. Error messages: Errors: 1. The reporter specified is not a user. 2. User 'testUser' does not exist. 2016-06-10 17:17:00,045 atlassian-scheduler-quartz1.local_Worker-1 ERROR anonymous [jira.issue.recurrence.RecurringIssueExecutor] CloneIssue action failed for issue TEST-408. Error messages: 1. Could not clone issue because of unexpected error. Please contact with your Jira administrator |
If you find problems that you can't solve with Jira proper configuration then create the ticket with logs details at https://codedoers.atlassian.net/projects/SUPPORT
...
Can't see repeating issue section on issue details view.
Repeating Issues require user to have issue edit permissions. If the user is not permitted to edit the issue the user will not be able to see repeting issue section in the right panels on issue details view. Repeat action in more menu will be not available also.
...
How to determine cloned issue due date?
Versions >= 0.7.0
User can schedule "Clone Issue" action for issue create date or issue due date by choosing proper "repeat by" option. There is also field where issue duration could be set in days.
When set-up new repating for issue add-on will calculate and set issue duration field based on original issue as working days between original issue create date and original issue due date. If original issue has not due date then issue duration field will have value equal 0. User can always change this value to other before save the repeating.
...
Repeating Issues add-on project roles are configured with jira-users and jira-developers groups as default members. Admin can add new default members for each role as described in Jira documentation: Specifying 'default members' for a project role. Please note that changing a project role's default members does not affect the actual project role members for projects already created. It is only template when new project is created. Existing projects need to be updated following to this documentation Managing project role membership.
...