Terminology issue... 'fixed' tickets

[daniel]

'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.

[daniel]

Noone else seems to mind. :)

[anonymous]

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.

[daniel]

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

[anonymous]

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

[trac@…]

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

[asmodai@…]

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';

[asmodai@…]

Change code occurences for fixed to resolved

[asmodai@…]

database upgrade

[asmodai@…]

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.

[Christian Boos]

…

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 ;)

[sid <sid.wiesner@…>]

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

[osimons]

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?

[matt_callaghan@…]

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?

[osimons]

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?

[osimons]

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.