...
How the "Issue Workflow" action work?
"Issue Workflow" action allows to run any status transition on the issue that can be executed manually from JIRA issue view. It works the same as clicking on available workflow transition: 'Start Progress', 'Close', 'Reopen' or any other transitions defined in the workflow related with the issue.
It means for example:
There is simple workflow that allow for below status transitions:
- OPEN > IN PROGRESS (transition 'start progress')
- IN PROGRESS > CLOSED (transition 'close')
- CLOSED > OPEN (transition 'reopen')
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.
Versions < 0.3.0
The Repeating Issues add-on does not allow to set exact time when specific action for given issue will be executed. Add-on allow users to define only days when repeating action should be applied. Actions are executed automatically every day at ~00:15 am.
How to get more logs from Repeating Issues?
Please go to Jira Administration > System > Logging and profiling. Above the packages please click on "Configure logging level for another package" link to add new package com.codedoers with the DEBUG Logging Level.
Could not execute recurrence because of unexpected error - what to do?
If you see any kind of message like "Could not execute recurrence because of unexpected error. Please contact with your Jira administrator" or "Could not clone issue because of unexpected error. Please contact with your Jira administrator" please ask your jira administrator to check Jira logs at time when the repeating should occurs.
There should be more detailed messages what exactly happens and why the recurrence fails. Administrator should find for logs like this:
| 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.
FAQ list
...
| Child pages (Children Display) |
|---|