#3320 new enhancement

Custom fields can't be hidden

Reported by:	coderanger@…	Owned by:
Priority:	normal	Milestone:	next-major-releases
Component:	ticket system	Version:	devel
Severity:	minor	Keywords:
Cc:	coderanger@…, goncha@…	Branch:
Release Notes:
API Changes:
Internal Changes:

Description

Though this is already fixed in the new workflow branch, it would be nice to fix this for 0.10.

All that needs to be done is add to following here :

'skip': config.getbool(name + '.skip', False)

Change History (11)

comment:1 by Christian Boos, 19 years ago

Owner:	changed from Jonas Borgström to Christian Boos
Severity:	normal → minor

If that's consistent with what's done in WorkFlow, I see no problem in adding this.

comment:2 by coderanger, 19 years ago

I think it may be called .hidden in WorkFlow.

comment:3 by anonymous, 19 years ago

Cc:	coderanger@… added

follow-up: 6 comment:4 by Christian Boos, 19 years ago

Hm, well, then I'm not sure it's worth introducing it for 0.10… What do others think?

comment:5 by coderanger, 19 years ago

I do currently have a workaround, but its rather gross. The code is here. Specifically the post-request filter, and the code in __init__ that magically adds it to the filters list.

in reply to: 4 comment:6 by Emmanuel Blot, 19 years ago

Replying to cboos:

Hm, well, then I'm not sure it's worth introducing it for 0.10… What do others think?

IMHO, we should not add any new feature at this point for 0.10, only bug fixing. This feature does not seem essential, so it can be postponed up to 0.11

comment:7 by Christian Boos, 19 years ago

Milestone:	0.10 → 0.11
Owner:	changed from Christian Boos to Alec Thomas

Ok, so let's defer that to the WorkFlow merge.

comment:8 by coderanger, 18 years ago

This has been implemented in the SimpleTicket plugin for the most part, though for custom fields that should never be seen it may still be worth adding.

follow-up: 10 comment:9 by Christian Boos, 16 years ago

Cc:	goncha@… added
Milestone:	0.11.2 → 0.12

It's also in the #2288 patch from goncha (attachment:trac-ticket.patch.gz:ticket:7349 )

(I hope you don't mind being added to the CC:).

in reply to: 9 comment:10 by goncha@…, 16 years ago

Replying to cboos:

(I hope you don't mind being added to the CC:).

Of course not.

comment:11 by Ryan J Ollos, 10 years ago

Owner:	Alec Thomas removed

Modify Ticket

Change Properties

Summary:
Description:	Though this is already fixed in the new workflow branch, it would be nice to fix this for 0.10. All that needs to be done is add to following [source:trunk/trac/ticket/api.py@3444#L161 here]: {{{ #!python 'skip': config.getbool(name + '.skip', False) }}} You may use WikiFormatting here.
Type:		Priority:
Milestone:		Component:
Version:		Severity:
Keywords:		Cc:	Set your email in Preferences
Branch:
Release Notes:
API Changes:
Internal Changes:

Action

leave as new The ticket will remain with no owner.

unassign The ticket will be disowned.

resolve as The resolution will be set. Next status will be 'closed'.

assign The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Your email or username:

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

You may use WikiFormatting here.

Download in other formats:

Context Navigation