I'm looking for a part-time remote job.

Hire me

I'm the author of:

Mastering Redmine is a comprehensive guide with tips, tricks and best practices, and an easy-to-learn structure.

Check the book's project or

Buy the book

Social pages of the book:

By buying this book you also donate to Redmine (see this page).

Follow me:

Improvement #1107

Change default project/issue/activity if no task is available

Added by Andriy Lesyuk about 13 years ago. Updated almost 13 years ago.

Target version:
Start date:
09 Nov 2010
Due date:
% Done:



Currently we have these six contexts: MainProject, MainIssue, MainActivity... Project, Issue and Activity. Main* contexts allow setting default project, issue and activity. And Project, Issue and Activity contexts allow setting project, issue and activity for a task.

Task context work the following way:
  • If there is a current task - set project, issue or activity for this task
  • If there is no current task but last task was finished less than 30 minutes ago - set project, issue or activity for last task
However sometimes users are trying to set default project, issue or activity using Project, Issue or Activity contexts... So looks like a good idea is to allow setting them. So another "option" should be added:
  • If no current task and last task is too old - set default project, issue or activity...

Of course, in this case and in case of setting project, issue or activity for a last task a warning should be written, e.g.:

Orangutan: No current task so setting it for last task...
Orangutan: No current task so setting default ...

Maybe also merge MainProject and Project contexts into a single one, MainIssue and Issue into a single one etc...


#1 Updated by Andriy Lesyuk almost 13 years ago

  • Project changed from Orangutan to Orangutan::Redmine

Also available in: Atom PDF

Terms of use | Privacy policy