It's all about the answers!

Ask a question

HELP!!!.. required fields are killing us.. solved, customer provided workaround

sam detweiler (12.5k6194201) | asked Apr 16 '13, 12:08 p.m.
edited Apr 21 '13, 10:30 a.m.
we need to turn on required fields for defects for our 160 projects..  but this is causing a fatal production line stop.
  1. the earliest state is New.. but we have a ton of workitems in New state. and they get fiddled with while in New state. we need a required on Create action.
  2. you cannot change a block of workitems (bulk) when u have to change 5 fields.
  3. IF we were forced to use NEW.. I need NEW from today forward.. not all the existing workitems.

we are on rtc not 4.0.1/.2 (ie, not current)


Kevin Ramer commented Apr 16 '13, 12:15 p.m.

It's my understanding that not burrowing into the hierarchy of the Required Attributes pre-condition would make the required attributes required on any save.

Daniel Toczala commented Apr 16 '13, 3:41 p.m.


  If you make fields required, then the existing defects will need these fields set the next time that they are saved.  Now that would mean that you would not be able to do a bulk change (since you can only specify a single field), which makes sense to me.  Is the issue that you want the current batch of defects NOT have these fields required, but any new defects to have these fields required?  Is the issue that people don't know the proper values to assign to these required fields in the existing defects?  Is it both things?

sam detweiler commented Apr 16 '13, 6:16 p.m.

Yes, it is both things.  we have run for 18 months with no structure of required fields and are starting to do enforcement now, but there is a lot of cleanup.
some of the required fields are new in the template (Detected By, who reported it)
and a product Feature field (that has to be customized for each project).  so the developers never saw them and knowing WHO reported the issue 1 month ago may be hard to figure out.

and we only added 4 required fields!..
detected by
and Found In - many teams have not been diligent in using this field, cause it really doesn't represent our way of working.

so, while I agree that we need to cleanup, we also need to be able to move forward reasonably.. cleanup is extra work.

Accepted answer

permanent link
Stephanie Bagot (2.1k1513) | answered Apr 17 '13, 3:29 p.m.
PMR 45487,7TD,000 was created to track this question. Support will continue working with Sam on this issue.
Stephanie Bagot selected this answer as the correct answer

5 other answers

permanent link
Geoffrey Clemm (30.1k33035) | answered Apr 16 '13, 11:37 p.m.
edited Apr 16 '13, 11:38 p.m.
One workaround is to create a new work item type with the required fields, and prevent your users from creating instances of the old work item type.

sam detweiler commented Apr 17 '13, 1:46 p.m.

ouch.. we have enough trouble managing the existing workitems..

permanent link
Ralph Schoon (62.7k33643) | answered Apr 17 '13, 3:57 a.m.
Another thought would be to define a role e.g. Admin for you and your team as admin that does not enforce the required attributes. Then do your cleanup and assign reasonable values.

All other roles will retain the requirement for the required attributes and will have to update work items as they go.

I find this the cleanest thing to do. It enforces to set the required attributes when users want to save, but it allows you to operate as required.

permanent link
sam detweiler (12.5k6194201) | answered Apr 17 '13, 1:45 p.m.
sorry, Ralph

I need to turn it OFF for all users of OLD (prior to today) workitems,
and ON for all users of all workitems created today and forward.

then the teams (across our 3500 people) can clean up the OLD workitems as they can.

Ralph Schoon commented Apr 17 '13, 1:53 p.m.

Then I think you have to disable it completely and run fixes with a queries before enforcing them again or follow Geoffs suggestion. 

permanent link
sam detweiler (12.5k6194201) | answered Apr 21 '13, 10:28 a.m.
edited Apr 22 '13, 11:11 a.m.
PMR results (not surprizing) 'working as designed', I am not keen that they copied the results from the forum answers above as 'the answer'.

so, I took the source code and added 2 lines of code and one XML element..  now it does what we need.
(I didn't try to update the advisor configuration UI) We will install our version along with the product version.
the product version will do required fields for ending states, regardless of prior state ('New' state with prior state of 'New'). Ours will check for being created. ('New' end state, with no prior state.)

so the advisors work like this (joining all the required fields lists together)

all workitems  
  + all of this type
     + all in this (ending) state
         + being created   - new capability  (ours)

can someone change the accepted answer to this entry

I 'could' completely replace the original function with our plugin, but the test requirements go crazy.

permanent link
sam detweiler (12.5k6194201) | answered Apr 22 '13, 1:18 p.m.
edited Apr 22 '13, 1:19 p.m.
I have opened this enhancement request

Your answer

Register or to post your answer.