Modify

Opened 6 years ago

Closed 5 years ago

#4788 closed enhancement (wontfix)

Rename "Blockedby" and "Blocking" to "Master-ticket" and "Sub-tickets"

Reported by: mauzer_tim Owned by: coderanger
Priority: normal Component: MasterTicketsPlugin
Severity: normal Keywords: MasterTickets, Agilo
Cc: Trac Release: 0.11

Description

Names of fields "Blocked By" and "Blocking" are a bit confusing and a bit ambiguous for a newbie especially if you are a non native English speaker. For example when I tried to explain goal of these 2 fields to my team, first I mixed up functions of these 2 fields, because they look and read similarly and its hard to understand their function at a glance.

What do you think about renaming them to something more clear, for example: "Master-ticket" and "Sub-tickets"? Moreover "master-ticket" sounds similar to the name of the plugin and it makes this name more consistent.

P.S. coderanger, thank you very much for so great add-on!

Attachments (0)

Change History (6)

comment:1 Changed 6 years ago by mauzer_tim

  • Type changed from defect to enhancement

comment:2 Changed 6 years ago by coderanger

  • Resolution set to worksforme
  • Status changed from new to closed

You can set the label to whatever you want.

comment:3 Changed 6 years ago by anonymous

I know and I have already done this. However there are 2 issues with this:

  1. In queries, in emails and in changes we see the old names.
  2. I understand that one can mechanically remind on frequent using what every from these fields does, but the main idea of suggestion is to make things easier for newbie.

comment:4 Changed 5 years ago by anonymous

  • Keywords MasterTickets Agilo added
  • Resolution worksforme deleted
  • Status changed from closed to reopened

Please allow the database custom field names for "blocking" and "blockedby" to be specified in trac.ini in the [mastertickets] section.

Possible default:

[mastertickets]
ticket_custom_field_masterticket = blocking
ticket_custom_field_subticket = blockedby

Reason:

Other plugins may need to integrate with a specific internal custom field name. (For instance, the AgiloForScrumPlugin currently uses "o_ref" and "i_ref" to do things similar to MasterTicketsPlugin -- I am also asking Agilo to allow for customizability).

This change would also allow the original creator of this ticket to use names meaningful to his team.

Chris

comment:5 Changed 5 years ago by pizzaman383

I'll second the request. We changed the source to have the field names in queries match what we wanted.

comment:6 Changed 5 years ago by coderanger

  • Resolution set to wontfix
  • Status changed from reopened to closed

I have no intention to change this. Trac already allows setting field labels. Any bugs in that system should be reported to Trac.

Add Comment

Modify Ticket

Action
as closed The owner will remain coderanger.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.