Issue Details (XML | Word | Printable)

Key: JRA-3319
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Per Mellqvist
Votes: 6
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
JIRA

Separate configuration of Issue Fields for create and edit issue

Created: 04/Mar/04 01:22 PM   Updated: 16/Sep/04 11:19 AM
Component/s: Administration
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Part
 
Reference
 

Participants: Owen Fellows, Per Mellqvist and William Crighton
Since last comment: 3 years, 51 weeks, 1 day ago
Labels:


 Description  « Hide
All of our employees are allowed (or even encouraged to report bugs. However only people in the tech department may edit the issues.

We want the initial information to be as easy to enter as possible and therefore we want the Issue Fields to be very few (Summary, Type, Priority, Description).

The issues are then reviewed and assigned by the project lead. At this point being able to fill in more information, such as due date, original time estimate etc is useful.

In order to make this work better it would be nice if the Issue Field configuration could be made separate for "Create Issue" and "Edit Issue"



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
William Crighton added a comment - 16/Sep/04 07:50 AM
I disagree that this issue 'duplicates' JRA-2372 as 2372 talks about field visibility/required'ness during transitions and this only covers field visibility/required'ness during create/edit.

Both would be nice though.


Owen Fellows added a comment - 16/Sep/04 11:19 AM
Change link to JRA-2372 to "relates to" instead of "duplicates".