Feature #7319

Repetitive tasks ?

Added by Frank Helk almost 7 years ago. Updated almost 2 years ago.

Status:NewStart date:2011-01-13
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution:

Description

The issue just came up to me, while I was doing some work that comes up every quarter.

I have some tasks coming up endless cycling, i.e. the preparation of mothly/quartery/yearly reports.

I would appreciate

  • a type of tracker that goes back to some "open" state (preferably "assigned") on predefined intervals, or
  • some kind of facility that spawns a new ticket at those predefined intervals

The definiton part could be an extension to the "new ticket" form, i.e.

[  ] Resurrect ticket every [<num>] [days/weeks/months/years], beginning on [date], to status [...].

or

[  ] Repeat ticket creation every [<num>] [days/weeks/months/years], beginning on [date].

There should be a special permission to make tickets repetitive, and management could be done on the standard ticket edit form.


Related issues

Related to Redmine - Feature #1176: Recurring Tasks New 2008-05-05

History

#1 Updated by Tomasz Sawicki about 6 years ago

Same as #1176?

+1 by the way..

#2 Updated by Etienne Massip about 6 years ago

Tomasz Sawicki wrote:

Same as #1176?

Not exactly, thanks for pointing out this relationship.

#3 Updated by Frank Helk over 5 years ago

I've described a way to do both this and #1176 in issue #1176 ...

#4 Updated by Luc GIROUX almost 5 years ago

+1

#5 Updated by Adrian Rotaru almost 5 years ago

+10

#6 Updated by Martin G over 4 years ago

+1

#7 Updated by Leonardo Salgado over 4 years ago

+1

#8 Updated by Dotan Cohen about 4 years ago

Please make clear how this issue differs from #1176. Thanks.

#9 Updated by Frank Helk about 4 years ago

OK - I've read again over this ticket and #1176 along with the comments and contemplated over 'em.

The requested features look similar, and I admit that they basically propose the same thing. I presume that if the feature gets implemented in a way like I've outlined it detailed in #1176#note-46, it will probably fit both requests good enough to satisfy both.

#10 Updated by Frank Helk almost 2 years ago

Any news on that ?

I'm still in need for that ...

Also available in: Atom PDF