Re: [opensource-dev] [JIRA] 'Affects viewer' use
Fixed. Thanks for the suggestion! On 2 May 2010 06:59, Kent Quirk wrote: > I don't see why we have that instruction. If you've tested on multiple > versions, we'd love to know that. So yes, affects version can be > multi-selected. You should only check items that you actually have tested. > > I'll ask someone to modify the text there. > >Q > > On May 1, 2010, at 8:43 AM, Opensource Obscure wrote: > > > > > What I'm supposed to do when I verify that a bug filed > > against Viewer 2.0 also affects Viewer 2.0.1 ? > > > > Should I really file a new, almost identical new ticket > > for Viewer 2.0.1? > > > > This seems to be the meaning of the "Please ONLY select > > a single version" phrase that appears near the > > "Affect Version" field (or not - see below) > > > > However, this doesn't look feasible and sustainable to me: > > it's time-consuming and -worst- all feedback, comments > > and votes get lost. > > > > Admittely, I never acted this way, and I always checked > > more than a version when appropriate; also, my feeling > > is that is the common behaviour on JIRA. > > > > Maybe I'm just wrong about Releases and Versions? :) > > maybe what the phrase actually means is that using > > the same ticket for Viewer 2.0 and Viewer 2.0.1 is OK; > > but if the same behaviour affects Snowglobe or other > > branches, a new different ticket should be filed? > > > > thanks in advance for clearing my mind.. > > > > opensource obscure > > ___ > > Policies and (un)subscribe information available here: > > http://wiki.secondlife.com/wiki/OpenSource-Dev > > Please read the policies before posting to keep unmoderated posting > privileges > > ___ > Policies and (un)subscribe information available here: > http://wiki.secondlife.com/wiki/OpenSource-Dev > Please read the policies before posting to keep unmoderated posting > privileges > ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
Re: [opensource-dev] [JIRA] 'Affects viewer' use
I don't see why we have that instruction. If you've tested on multiple versions, we'd love to know that. So yes, affects version can be multi-selected. You should only check items that you actually have tested. I'll ask someone to modify the text there. Q On May 1, 2010, at 8:43 AM, Opensource Obscure wrote: > > What I'm supposed to do when I verify that a bug filed > against Viewer 2.0 also affects Viewer 2.0.1 ? > > Should I really file a new, almost identical new ticket > for Viewer 2.0.1? > > This seems to be the meaning of the "Please ONLY select > a single version" phrase that appears near the > "Affect Version" field (or not - see below) > > However, this doesn't look feasible and sustainable to me: > it's time-consuming and -worst- all feedback, comments > and votes get lost. > > Admittely, I never acted this way, and I always checked > more than a version when appropriate; also, my feeling > is that is the common behaviour on JIRA. > > Maybe I'm just wrong about Releases and Versions? :) > maybe what the phrase actually means is that using > the same ticket for Viewer 2.0 and Viewer 2.0.1 is OK; > but if the same behaviour affects Snowglobe or other > branches, a new different ticket should be filed? > > thanks in advance for clearing my mind.. > > opensource obscure > ___ > Policies and (un)subscribe information available here: > http://wiki.secondlife.com/wiki/OpenSource-Dev > Please read the policies before posting to keep unmoderated posting privileges ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
[opensource-dev] [JIRA] 'Affects viewer' use
What I'm supposed to do when I verify that a bug filed against Viewer 2.0 also affects Viewer 2.0.1 ? Should I really file a new, almost identical new ticket for Viewer 2.0.1? This seems to be the meaning of the "Please ONLY select a single version" phrase that appears near the "Affect Version" field (or not - see below) However, this doesn't look feasible and sustainable to me: it's time-consuming and -worst- all feedback, comments and votes get lost. Admittely, I never acted this way, and I always checked more than a version when appropriate; also, my feeling is that is the common behaviour on JIRA. Maybe I'm just wrong about Releases and Versions? :) maybe what the phrase actually means is that using the same ticket for Viewer 2.0 and Viewer 2.0.1 is OK; but if the same behaviour affects Snowglobe or other branches, a new different ticket should be filed? thanks in advance for clearing my mind.. opensource obscure ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
