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:

Feature #180

Issue status changing

Added by Andriy Lesyuk over 9 years ago. Updated over 8 years ago.

Status:
Open
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
Due date:
% Done:

0%


Description

As far as most of the work with an issue is going to be done using Orangutan it would be very useful to be able to change issue status using some special context.

Some samples and ideas:

User: #128 is new
User: Resolve #128
User: Close #128

In addition the context should be called when issue is changed to be 100% done (e.g.). Of course, it should ask for confirmation:

Orangutan: So should I change its status to "Closed"?
User: Yes
Orangutan: Ok.

History

#1 Updated by Andriy Lesyuk about 9 years ago

  • Priority changed from Minor to Normal

#2 Updated by Andriy Lesyuk about 9 years ago

  • Target version set to 1.07

#3 Updated by Andriy Lesyuk about 9 years ago

Another suggestion:

If user adds hours to an issue and issue status is new Orangutan can ask:

Orangutan: Maybe I will change status to "In Progress"?
User: Sure
Orangutan: Done

#4 Updated by Andriy Lesyuk almost 9 years ago

  • Target version changed from 1.07 to 1.05

#5 Updated by Andriy Lesyuk almost 9 years ago

  • Target version changed from 1.05 to 1.07

#6 Updated by Andriy Lesyuk over 8 years ago

  • Project changed from Orangutan to Orangutan::Redmine

Also available in: Atom PDF

Terms of use | Privacy policy