Project

General

Profile

Actions

Feature #514

closed

Custom Field on Closing Screen

Added by Robert Hallock over 16 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Duplicate

Description

Redmine has been a massive help to our company in keeping track of issues, and I would first like to reiterate my thanks
for the time and effort you have put forth on this project, JPL.

That said, there's a feature we'd really like to see:

When we close an issue, there are often actions that need to occur as a result of a ticket being closed, or procedures
that were followed during the course of a ticket's lifetime. For example, my firm has a standard set of troubleshooting
steps that apply to every issue we have, and we'd love to start tracking which troubleshooting step was key to fixing
the problem. Alternatively, this also allows us to track a trend of what the actual problem was, as opposed to just
the symptom

Having the ability to add custom fields to the ticket closing screen, independently of the issue addition screen, would
be massively helpful.

I appreciate any time or thought you put towards this request.

Thank you!


Related issues

Is duplicate of Redmine - Feature #703: Configurable required fields per tracker/status/roleClosedJean-Philippe Lang2008-02-21

Actions
Actions #1

Updated by Toshi MARUYAMA about 13 years ago

  • Category set to Custom fields
Actions #2

Updated by Go MAEDA about 7 years ago

  • Is duplicate of Feature #703: Configurable required fields per tracker/status/role added
Actions #3

Updated by Go MAEDA about 7 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

This request is covered by fields permission setting in workflow page which was implemented by #703 (Redmine 2.1.0).

Actions

Also available in: Atom PDF