Couple of possibilities

-  if these projects were created from template projects, examine whether the templates have differing workflow logic

-  check whether there is anything in the ActionCanExecute function on module entry that could be failing. When modules error, they cause downstream workflow logic to become unpredictable.

From a brute-force standpoint you could copy the entire defect workflow code from project A to project B (back up the original workflow code) and see if the problem can be reproduced.

I'll also put in a plug here for our Co-Pilot for ALM suite of applications, specifically because for workflow troubleshooting and maintenance it has four important capabilities that can help - some screenshots are shown in the data sheet attached.

• cross-project configuration comparison ( compare fields between projects)
• cross-project workflow comparison and difference viewer
• workflow visualization and tracing
• smart search in workflow files

PDF

Thank you for your reply; I appreciate it.

The project was created from another project, not a template.

There is no customization in ActionCanExecute.

I copied workflow code from our other installation for WizardFieldCust_Details and WizardFieldCust_Ad for the groups I have access to (including TDAdmin) but it still does not change what appears for a new defect or when displaying an existing defect.     

Thanks for the info on Co-Pilot; I've passed that along to our QA Manager.

No problem.

Is there any additional code being run from the Bug_New or Bug_MoveTo subroutines that might be being executed after the WizardFieldCustDetails or WizardFieldCust_Add calls?  Those might be interfering or cancelling out what's the Wizard subroutines are doing.

The only customization is for Bug_AfterPost and Bug_FieldCanChange but the wizard doesn't impact them.  There were a number of user groups not being used, which made the workflows large.  In case that was complicating things, I removed those groups since we don't use them, regenerated the Add and Details workflow via the Wizard, then checked again.  I really didn't think it would make a difference but tried anyway.  It didn't make a difference.  

Very odd.  What version of ALM are you using.  You may want to open a ticket with support if you suspect a technical issue.

In our engagements I avoid using the wizards for field layout customizations, I find that they are hard to maintain and troubleshoot especially as the number of groups and custom fields increases.

If you look at the code in the ALM Demo project, they take a different approach, something like this.

' Show the New Defect dialog and apply the field layout
' 
Sub Bug_New
    Fields = Bug_Fields
    NewDefect_SetFieldsLayout
End Sub

' Set the field layout by user group
'
Sub NewDefect_SetFieldsLayout
 
    ResetFields
    SetFieldsLayout_Common
    
    If User.IsInGroup("QATester") Then
        SetFieldsLayoutQA
    End If
    
End Sub

' Set the field layouts for fields that are common to all groups
'
Sub SetFieldsLayout_Common
  SetFieldProperties "BG_SUMMARY", True, True, 0, 0
  SetFieldProperties "BG_DETECTED_BY", True, True, 0, 1
  SetFieldProperties "BG_DETECTION_DATE", True, True, 0, 2
End Sub

' Set the field layouts for fields for the QA group
'
Sub SetFieldsLayout_QA
  SetFieldProperties "BG_USER_01", False, True, 0, 10
  SetFieldProperties "BG_USER_02", False, True, 0, 11
End Sub


' Reset all fields so they are not visible. There are other ways to do the
' same thing.
Sub ResetFields
    For i = 0 to Fields.Count
        Fields.FieldById(i).ViewOrder = 100
    End For
End Sub

' Common routine for setting the field properties including visibility, view order, etc
Sub SetFieldProperties (FieldName, FieldRequired, FieldVisible, FieldPage, FieldOrder )
  Fields(FieldName).IsVisible = FieldVisible
  Fields(FieldName).IsRequired = FieldRequired
  Fields(FieldName).PageNo = FieldPage
  Fields(FieldName).ViewOrder = FieldOrder
End Sub

15.5.1 for the installation where this project is that is causing issues.  I like that way of coding the workflow; I might try something like that.  We have no differences in what fields are displayed based on the groups or whether it is a new or existing defect.

Update - even though I knew the project wasn't created from a template, I had a thought this morning, triggered by your question if the project was created from a template, that maybe it was created from a project that was created from a template.   Some background...  this project I'm working on is in an ALM environment of a company that my client purchased, so I'm not totally familiar with everything they have done in the past.  My client has not really used templates, so I'm not used to looking at that part of the workflow.  

So this morning I thought I would look at the template workflow and low and behold, there was the problem!   I updated the template workflows and badda bing, we are good to go!   

Thank you!  We are all good now, and I really appreciate your inputs!