I agree, we need to ensure that open BUG type jira have 'Affects Version' and fixed ones need to have 'Fix Version' set.
Thanks for link Wei, thats very useful. It would be great if we can make Affects Version mandatory for BUG type jiras. I took a quick look and was confused on how to make the change! Regarding 'Fix Version', it makes to set that only when the bug is being marked fixed. However, it is not clear if enforcing that during that transition of jira is possible. Forcing it to be set before its actually fixed does not help, it only increases the chances of having a wrong Fix Version set, which is probably worse than having no fix version at all. On Thu, Oct 15, 2015 at 8:51 PM, Wei Zheng <wzh...@hortonworks.com> wrote: > Looks like it's configurable. > > https://confluence.atlassian.com/jira/specifying-field-behavior-185729654.html#SpecifyingFieldBehavior-Makingafieldrequiredoroptional > > Thanks, > Wei > > > > > > > > On 10/15/15, 13:58, "Eugene Koifman" <ekoif...@hortonworks.com> wrote: > >>Can JIRA be made to enforce that these are set to something when the >>ticket is Resolved? >> >> >>On 10/15/15, 9:52 AM, "Xuefu Zhang" <xzh...@cloudera.com> wrote: >> >>>Hi folks, >>> >>>I know most of us have done a good job in updating JIRAs with respective >>>"Affects version/s" and "Fix version/s". However, I do see from time to >>>time that these fields are missing in some JIRAs even after those JIRAs >>>are >>>closed. >>> >>>These field are very important in helping users to determine if their >>>versions are affected or fixed. >>> >>>If for some reason either the field is not applicable, please use "n/a" >>>specifically. >>> >>>Please feel free to share your thoughts or comments on this. >>> >>>Thanks, >>>Xuefu >> >>
