Note that there are some explanatory texts on larger screens.

plurals
  1. USThanizer
    primarykey
    data
    text
    plurals
    1. COMy question was poorly phrased. Our organization is working on product beta releases that our customers can receive (there is Beta1, Beta2, and Beta3). In order to provide support, each beta version has its own Service Pack branch hanging off Main with a Release branch hanging off each one. If a bug is found, the relevant branch is fixed (SPBeta1, SPBeta2, SPBeta3, Dev. This allows us to support all beta versions.) Regardless of our branching strategy, is it possible to add a field to work items whose list items are dependent upon branches in a particular team project?
      singulars
    2. CO@Blender, wow. That did it. I never would have thought... Can you make that an answer and I'll accept it?
      singulars
    3. COThe question is honestly this: Regardless of our branching strategy and regardless of the type of work item (a bug is an example. This should apply to any work item), is it possible to add a field to work items whose list items are dependent upon branches in a particular team project so that developers can easily find the branch they need develop on when going through their work items? The scope of the question is focused on developers and our branching strategy (which, I know is weird, but it's how we are doing it.)
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload