Versions Compared

Old Version 18

changes.mady.by.user Mateusz Daleki

Saved on

compared with

New Version 19

changes.mady.by.user Mateusz Daleki

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Setup repeating details

  1. Go to issue view .

  2. Select More > Repeat 

    Select More > Repeat from issue action navigation bar or

    click 

    click Set repeating

     in 

     in Repeating Issue section

     on

     on the right panels.

    Image Modified

  3. On repeating configuration dialog please

    select 

    select Create Sub-task

     for

     for repeat action field.

    Image RemovedImage Added

Configuration fields for Create Sub-task action

Field name

Description

Reporter

User which will be set as reporter of new sub-task in parent issue.

Info

  • This is not the creator of new issue. The creator of new issue will be the user who set-up repeating. See Which user is used by the Repeating Issue app during processing?

  • This field is only visible when creator has permission to modify reporter of new issues. If creator can't modify reporter then he will be set as reporter

Assignee

User which will be set as assignee of new cloned issue.

Remove me from watchers

When selected - the creator will not be notified of any changes to new sub-task issue.

Info

  • This field is only visible if watching is enabled in Jira General Configuration > Options > Allow users to watch issues

  • Creator will be removed from watchers only if he has "Manage watcher list" permission in project

Summary

Summary that will be set to new sub-task issue.

This field can have parameters like ${repeatingDate} - for details please

follow 

follow Available tokens in action param strings

Repeat for

Defines which issue date should be repeated: issue create date or issue due date.

For example if issue duration is 2 days, and the repeating occurence falls

on 

on 10 January 2017

 then

 then:

when 

  • when issue create date

 is

  •  is selected - new sub-task issue will be created

at 

  • at 10 January 2017with due date equal 12 January 2017 (due date is calculated to be 2 days after)

when 

  • when issue due date

 is

  •  is selected - new sub-task issue will be created at 8 January 2017 with due date

equal 

  • equal 10

January 2017 

  • January 2017 (create date is calculated to be 2 days before)

Info

Issue create date and issue due date is calculated with non-working days adherence. For details read Managing non-working days

Issue duration

The number of working days between new sub-task issue created date and due date.

Please

read 

read how to configure non-working days.

Issue type

Issue type of new created sub-task.

Component/s

Project components which will be set to new sub-task issue.

Description

Description that will be set to new sub-task issue.

This field can have VTL expression like $repeating.date - for details please

follow 

follow Velocity references in field values

Notify watchers

When selected -

 watchers

 watchers of parent issue will be notified via email. See Email notifications.

Note

Note that watchers will be notified only when the repeating had been setup by user who has 'View voters and watchers' or 'Manage watcher list' permission in the project. Please read the Jira documentation - Managing project permissions on how to edit permissions.

Mute success notifications

When selected -  notifications of correct execution will not be sent. See Email notifications.

Other system and custom fields

After clicking "More..." on repeating issue dialog more system and custom fields defined in Jira will be available. Each field will have simple form input where static value or dynamic value can be provided - see Velocity Template Language in Repeating Issues add-on.