![]() ![]() ability to have recurrence schemes copied regardless of whether individual issues or whole projects are copied,.ability to recur with or without subtasks,.properly handling issue attributes, including keeping: parent, custom fields, priority and resetting: done ratio, time entries and status,.updating both start and due dates according to schedule (if specified),.ability to specify recurrence based on start or due date for recurrence based on close date: ability to specify which of dates - start or due - is inferred from close date,.fixed date after last recurrence has been closed.last recurrence dates but only after it has been closed,.last recurrence dates if closed on time or close date otherwise,.creation of next issue recurrence by means of:.2nd working day of month or 1st to last working day of month), months with dates keeping the same working day (according to non-working week days specified in Redmine settings) from the beginning or to the end of the month (e.g.2nd Tuesday of month or 1st to last Friday of month), months with dates keeping the same day of week from the beginning or to the end of the month (e.g.months with dates keeping fixed distance from the beginning or to the end of the month (e.g.working days (according to non-working week days specified in Redmine settings),.specification of recurrence frequency by means of:.multiple recurrence schedules per issue possible (except for reopening recurrence calculated from close date, where only 1 schedule is possible),. ![]() recurrence creation/deletion directly from form on issue page (no separate page, no page reloading when creating/deleting recurrences),.The most notable features of this plugin include: Avoiding regressions and eliminating bugs is valued over new functionalities. Unusual situations are reported to user in a visible manner during use. Scheduling algorithms are tested for accuracy. Greatest emphasis in development is put on reliability. It was due to amount of changes would make it impossible to fit into original codebase. Thank you nutso! The code though was rewritten from scratch. ![]() This plugin has been inspired and based on nutso's plugin redmine-plugin-recurring-tasks. Issue tracker (you can register and login there with your Github account). Because some boring things have to be done on-time after all. Plugin creates new issue or reopens existing issue for each new recurrence. You need to repeat it as suggested above until you end at the current version.Plugin for Redmine to schedule Redmine issue recurrence according to a schedule (see Features below for possible scheduling options). Here you can read what to do in a single upgrade process: Moreover, you would need suitable plugin versions at the end. In case you run Redmine with plugins, you should move them out as long as you upgrade. įor older versions of Redmine you can try to get the same information via the wiki page history. You can read here about what Ruby, MySQL, Rails is required. Current supported versions of Redmine requirements ¶ Therefore, I would ignore them in as long as possible and care for them after the Redmine upgrade is done. ![]() Subversion and Apache ¶īoth, Subversion and Apache, should not be more stable with Redmine. Maybe start the first upgrade with the lowest version to be accepted by Redmine now or check what was the highest version of MySQL recommended for your current Redmine version and start with that. The required Bundler version should also be determined in the Redmine Gemfile when I remember right. I would upgrade it to the latest version but ignore it when running bundler for Redmine until you arrive the latest version. Redmine has the required Rails version defined in its Gemfile. You can remove Rails 2.3.14 if it is installed independently of Redmine. RubyGems does not need to be installed explicitly but I do not know from which Ruby version ongoing this is true.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |