Why have fix version allow multiple values instead of one?

I've been trying to figure out what the thought process behind this is and I just can't find a scenario where this makes sense... I'm reluctant to just change it to a single-value field until I know how other people use this multi-value field. Plus it's a pain to go through the default workflows and update all the code that requires this field to be multi-value.

Thanks!
4 comments
Comment actions Permalink
Hello Diego,

Talking about what is the actual case when multi-value "Fix version" field is needed, simple example is when fixed issue or newly implemented feature must be included in several versions. For example you have the latest 4.0 version of your product and at the same time you supports 3.5 version and 3.2 version. You have a new feature that you whant to be included in 4.0 and 3.5 versions, 3.2 is no longer supported. In this case you choose these both fix versions to be shown in "Fix version" custom field.

What challenges have you faced with the multi-value "Fix version" field VS. workflow?

Contact us if you have questions, we'll be happy to help you.
0
Comment actions Permalink
thanks! I was simply looking for the reasoning and you're right.. that makes perfect sense.
0
Comment actions Permalink
Diego,

You are welcome!

So, what difficulties have you experienced with workflows and multi-value fields?
0
Comment actions Permalink
no difficulties at all.. just was thinking to change it to single-value unless i could find reasoning for having multi-value and you provided that. thanks!
0

Please sign in to leave a comment.