Redmine Development Task Workflow - Bug Fix and Feature Requests

Redmine Development Task Workflow - Bug Fix and Feature Requests

Support Team enters new task in Redmine with a Project of Support, Tracker of Customer Support, and Assignee of Development. Support will choose either the Bug Fix or Feature Request template.

A member of the development team will check for new tasks under the development project as they come in. The team will also review any tasks under the Development project as part of their weekly code review meeting.

Upon review of the task, the task will be updated to have a tracker of Bug or Feature Request and be assigned to the appropriate project. If known at this time, the task will also be assigned to a member of the development team.

Once work begins on the task, the status will be set to In Progress. If the task is still assigned to the development team, the developer will assign the task to themselves.

If feedback on the task is needed from the author of the task or from other members of the team during development, the status will be set to Feedback and assigned to the appropriate party.

Upon completion of the development on a task and successful check-in to subversion, the status will be set to Resolved and Released To to Local Machine.

When tasks are released to the development and test environments, Released To will be updated to Development/Test as appropriate. The Target version will also be set on the tasks.

Upon completion of the central deployment, all tasks from the release will have Released To to Production and assigned back to their Author with a status of Feedback. The author will be responsible for any customer feedback. When the author is done with any follow-up, they will put a note in Redmine and change the status on the task to Closed.

 


    • Related Articles

    • Redmine Development Task Workflow - New Community Instance

      Support Team enters new task in Redmine with a Project of Support, Tracker of Customer Support, Assignee of Development, and New Community Instance template. A member of the development team will check for new tasks under the development project as ...
    • Redmine Development Task Workflow - Delete Practice Data

      Support Team enters new task in Redmine with a Project of Support, Tracker of Customer Support, Assignee of Development, and Delete Practice Data template. A member of the development team will check for new tasks under the development project as ...
    • Redmine Development Task Workflow - Customer Support

      Support Team enters new task in Redmine with a Project of Support, Tracker of Customer Support, Assignee of Development, and Customer Support template. A member of the development team will check for new tasks under the development project as they ...
    • Redmine Development Task Workflow - Support and Implementation Data Work

      Support Team enters new task in Redmine with a Project of Support, Tracker of Customer Support, and Assignee of Development. Support will choose either the Support Data Work or Implementation Data Work template. A member of the development team will ...
    • Workflow for Systems Tasks

      Workflow for Systems Tasks Overview Create a new Tracker task. Check out a working copy. Create a new branch. Make changes within the branch in your working copy. Test your changes. Fix problems discovered during testing. Commit your changes to the ...