[#JRA-2372] It would be nice to have an option to hide fields in 'Create issue' phase

JIRA

It would be nice to have an option to hide fields in 'Create issue' phase

Created: 19/Sep/03 03:43 AM Updated: 12/Jan/06 07:16 PM

Component/s:

None

Affects Version/s:

2.4.1

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue duplicates:

~~JRA-5793~~ Create Field Screens

Reference

This issue relates to:

JRA-1713 Bill As for work log

JRA-961 Make more use of time tracking features

JRA-3319 Separate configuration of Issue Fields for create and edit issue

This issue is related to:

JRA-5783 Make field required only for one state transition

Participants:	Bettina Zucker, Jeff Turner [Atlassian], Michael Ingeman-Nielsen, Mika Ruottinen, Nick Menere [Atlassian] and Owen Fellows
Since last comment:	121 weeks, 4 days ago
Resolution Date:	20/Oct/05 07:43 PM
Labels:

Description

« Hide

We have now an option to hide fields via Administration --> View Issue Field, but this feature hides the field from both 'Create Issue' phase and 'Edit Issue' phase.

What we need is a possibility to hide fields during the phase of creating issues, so that issue reporters cannot see all the fields available. These 'extra' fileds are updated (Edit Issue) during the phase when we are going thru the list of all newly reported issues.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Owen Fellows - 09/Nov/03 11:20 PM

If we are going to add events for customfields we could add them to the normal fields too. Worth considerding to do together to make the implementation consistent.

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 26/Nov/03 06:02 PM

Also, if a field like Component is hidden, it doesn't show up elsewhere, like the Browse Project page. It would be nice if a field could be read-only (not visible on creation or edit, but existing fields would display).

[ Permlink | « Hide ]

Owen Fellows - 02/Jan/04 09:51 AM

Would be good to pick fields to use for filtering on different reports e.g. timetracking.

[ Permlink | « Hide ]

Owen Fellows - 25/Mar/04 01:40 PM

Request from the mailing list.

---------------------------------------------------------------------
Hi Owen,

I don't know how to edit that link so I'll just mail you instead.

Other bug trackers like TeamTrack have the option of making any field
required or making it hidden on a per transition basis. For example, in
a previous company, I had a "Fixed in Build" field in my bug report.
When initially logging a bug, this field was hidden as it is not
relevant when a bug is found. However, when a developer was Resolving a
Bug in a later transition, this field was mandatory as he had to enter
the build of software the defect was fixed in.

[ Permlink | « Hide ]

Michael Ingeman-Nielsen - 20/Oct/05 03:36 AM

This would be a great feature. I have previously worked with the Census system where it was possible to hide, show or require fields in various parts of the workflow. It was great to work with, as it simplified the UI for the testers and developers without sacrificing the need for detailed information from each step.

[ Permlink | « Hide ]

Nick Menere [Atlassian] - 20/Oct/05 07:42 PM

Michael,

Sorry for the confusion but this issue should have bene closed.

As of 3.2 we have the ability to define screens for different stages of the workflow (creation included). You can define what fields appear on what screens.

I will resolve this issue as a duplicate.

Cheers,
Nick

[ Permlink | « Hide ]

Bettina Zucker - 12/Jan/06 05:09 AM

Hello Michael,

the issue discussed here is only partly a duplicate of ~~JRA-5793~~ Create Field Screens.
Hidden fields can now be defined on a per transition basis through the screens.
But what about mandatory fields?

Currently (I have Jira enterprise 3.3.3 as official system and 3.4.3 as test system)
if a field is mandatory, it is so from the beginning of the workflow to the end.

Take as an examle the fields "FixVersion(s)" or "Estimated Time".
The issue reporter first puts a dummy value in it, since she knows no better.
After this the field has some value, this means nobody anymore cares if it is mandatory.
The dummy value stays there until the issue is closed!

I want to state that a filed should be mandatorily set/changed in a screen.

Cheers + Thanks Bettina

[ Permlink | « Hide ]

Bettina Zucker - 12/Jan/06 08:52 AM

I just found out the mandatory fileds part of this discussion is already treated in JRA-5783.

[ Permlink | « Hide ]

Nick Menere [Atlassian] - 12/Jan/06 07:16 PM

Bettina,

A customer ahs posted some [code|]http://confluence.atlassian.com/display/JIRAEXT/JIRA+Workflow+Validators that will enable this.
It is a validator that will stop a transition if a field has not been entered.
Some code modifation will be needed to suit specific needs.

Cheers,
Nick