Edgewall Software
Modify

Opened 16 years ago

Closed 11 years ago

#194 closed defect (worksforme)

Terminology issue... 'fixed' tickets

Reported by: daniel Owned by: Jonas Borgström
Priority: normal Milestone:
Component: ticket system Version: devel
Severity: minor Keywords: workflow tickettypes
Cc: osimons, Christian Boos, matt_callaghan@… Branch:
Release Notes:
API Changes:

Description

'fixed' isn't a really good term for when you complete an ehancement request or finish a task.

A more generic term would be 'completed', which might be better for different kinds of issues (think tasks, issues, bug fixes, etc).

Examples:

  • The task is completed.
  • The bug is completed.
  • The enhancement is completed.

Vs:

  • The task is fixed.
  • The bug is fixed.
  • The enhancement is fixed.

Attachments (2)

resolved.diff (2.1 KB ) - added by asmodai@… 13 years ago.
Change code occurences for fixed to resolved
db20.py (274 bytes ) - added by asmodai@… 13 years ago.
database upgrade

Download all attachments as: .zip

Change History (20)

comment:1 by daniel, 16 years ago

Component: generalticket system
Severity: normaltrivial

comment:2 by daniel, 16 years ago

Summary: Terminology issue.,. 'fixed' ticketsTerminology issue... 'fixed' tickets

comment:3 by daniel, 16 years ago

Resolution: wontfix
Status: newclosed

Noone else seems to mind. :)

comment:4 by anonymous, 16 years ago

Resolution: wontfix
Severity: trivialnormal
Status: closedreopened
Version: 0.6devel

A resolution type of "fixed" just doesn't fit for enhancements, or other types of non-bugfix tasks.

Rather than "closed", I think a more reasonable new resolution type might be "completed".

If there isn't enough interest among the core developers to add this, could they please outline the scope of changes that would be necessary to implement it? Perhaps another can give it a shot, and provide a patch.

comment:5 by daniel, 16 years ago

Milestone: 0.7

someone minds. thanks for commenting. I agree with the previous poster. :)

comment:6 by anonymous, 16 years ago

Is it possible to enumerate a list with "completed" for enhancements/tasks tickets and "fixed" for bug tickets?

comment:7 by trac@…, 16 years ago

The timeline uses the syntax 'resolved'; is this not appropriate? It seems good to me, better than 'completed' even.

comment:8 by Jonas Borgström, 16 years ago

Milestone: 0.70.7.1

comment:9 by daniel, 16 years ago

Milestone: 0.7.11.0

comment:10 by asmodai@…, 13 years ago

The database uses the resolution status of fixed. So that either needs to stay, or we need to add an upgrade again to replace all occurences. Something like: UPDATE ticket SET resolution = 'resolved' WHERE resolution = 'fixed';

by asmodai@…, 13 years ago

Attachment: resolved.diff added

Change code occurences for fixed to resolved

by asmodai@…, 13 years ago

Attachment: db20.py added

database upgrade

comment:11 by asmodai@…, 13 years ago

As cmlenz commented:

so in the ticket screen you'd have "resolve as resolved"?

Which, indeed, sounds peculiar. But the attached patches should at least provide a basis should this get to be changed.

comment:12 by Christian Boos, 13 years ago

Milestone: 1.00.11
Severity: normalminor

Well, this hardcoded stuff is going to change anyway with WorkFlow. To facilitate migration, which could happen any time (when the admin decides to changes the workflow), it would probably be better to have a rename facility, in TracAdmin or WebAdmin (or both).

Still tentatively scheduling WorkFlow stuff for 0.11 ;)

comment:13 by sid <sid.wiesner@…>, 13 years ago

Keywords: workflow added

Add workflow keyword due to dependency mentioned by cboos in comment:12

comment:14 by Christian Boos, 13 years ago

Keywords: tickettypes added

in reply to:  12 ; comment:15 by osimons, 12 years ago

Replying to cboos:

Still tentatively scheduling WorkFlow stuff for 0.11 ;)

As all this is in trunk in time for 0.11 - with workflows and actions, and admin panels for resolutions. Is there anything left here that warrants keeping the ticket open?

  • Are we going to change default terminology?
  • Are we going to provide 'rename' tools for those who want to migrate existing database to some new terminology?

in reply to:  15 comment:16 by matt_callaghan@…, 12 years ago

Cc: osimons Christian Boos matt_callaghan@… added

We have interest in this default terminology rename. For example:

  • Change component to thing
  • Change Milestone to goal
  • etc..

Is there any way to do this currently or is there something in the works?

comment:17 by osimons, 11 years ago

With the workflow-related changes mentioned above + the i18n/l10n features of current trunk (0.12dev) to make a custom translation with own terms and phrases, I think that pretty much covers as much customization as this ticket and related discussion warrants.

I don't see any particular target to close this ticket against at this point, so suggesting a 'worksforme' based on current possibilities. Objections?

in reply to:  17 comment:18 by osimons, 11 years ago

Milestone: 0.11.3
Resolution: worksforme
Status: reopenedclosed

Replying to osimons:

I don't see any particular target to close this ticket against at this point, so suggesting a 'worksforme' based on current possibilities. Objections?

I suppose not. Closing.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Jonas Borgström.
The resolution will be deleted. Next status will be 'reopened'.
to as closed The owner will be changed from Jonas Borgström to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.