History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-6549
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Duplicate
Priority: Major Major
Assignee: Unassigned
Reporter: Sergio Castillo
Votes: 15
Watchers: 12
Operations

If you were logged in you would be able to see more operations.
JIRA

Allow to make fields required on per screen/workflow step basis

Created: 03/May/05 05:14 PM   Updated: 06/Apr/06 12:53 PM
Component/s: Workflow
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Environment: Standalone Enterprise
Issue Links:
Duplicate

Participants: Anton Mazkovoi [Atlassian], Bettina Zucker, Brian Nguyen, Carl Jones and Sergio Castillo
Since last comment: 109 weeks, 5 days ago
Resolution Date: 05/Apr/06 07:47 PM
Labels:


 Description  « Hide
it would be nice to have a workflow validator that checks for entry in fields.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Brian Nguyen - 03/May/05 11:54 PM
Do you mean you want to make sure a field has a particular value/s? Does a select list not provide this functionality?

Anton Mazkovoi [Atlassian] - 04/May/05 12:31 AM
In JIRA 3.2. it will be possible to compose screens (a group of fields) and display a screen on a workflow transition. Therefore it will be possible to select which fields are shown on each workflow transition. At the moment it is possible to make fields required to ensure they are populated using Field Layouts (whilch are renamed to Field Configurations in JIRA 3.2). In the Enterprise edition it is possible to setup on per project per issue type basis.

Woud you like to be able to configure that a field is required only for a certian workflow transition?


Sergio Castillo - 05/May/05 10:50 AM
Anton,

Yes, I would like to be able to configure that a field is required only for a certain workflow transition.

By the way, the possibility to compose screens and display a screen on a workflow transtion in JIRA 3.2 is a very nice feature.


Anton Mazkovoi [Atlassian] - 06/May/05 12:17 AM
Thanks for the feedback!

I have changed the summary of the issue to better reflect its meaning.

Please note that it is possible to write custom validators (in JIRA 3.0 and later) and use them in JIRA using its plugin system. Please refer to:
http://confluence.atlassian.com/pages/viewpage.action?pageId=11764

The tutorial refers to workflow Conditons and Post Functions, but Validators are very similar.


Bettina Zucker - 05/Apr/06 07:13 AM
Hello Anton,

it seems to me that this issue, especially after the summary change, is not only related to #JRA-5783.
It's a plain duplicate of it!

It would be better to mark it as a duplicate, so voters of this issue will shift their votes to the main issue,
and discussion will be in common.

About the validator solution check also issue #JRA-9088.

Cheers

Bettina


Anton Mazkovoi [Atlassian] - 05/Apr/06 07:47 PM
You are right.

Carl Jones - 06/Apr/06 12:53 PM
As an example, I want to require a comment when a developer Resolves an issue.
But comments can be optional in other transitions.
Is there a way to do that?
-carl