sweet, thanks! -igor
On Thu, Oct 28, 2010 at 10:12 AM, Brian Topping <[email protected]> wrote: > Fix version does not show now on create issue screen. > > On Oct 28, 2010, at 12:59 PM, Igor Vaynberg wrote: > >> i tweaked it, can you test? >> >> -igor >> >> On Thu, Oct 28, 2010 at 9:31 AM, Brian Topping <[email protected]> wrote: >>> Yes, but I believe that option is removed from the issue creation screen of >>> non-devs if they don't have that permission... >>> >>> On Oct 28, 2010, at 12:25 PM, Igor Vaynberg wrote: >>> >>>> no, the problem is reporters assign the fix version when they create >>>> the issue :) >>>> >>>> -igor >>>> >>>> On Thu, Oct 28, 2010 at 9:11 AM, Brian Topping <[email protected]> >>>> wrote: >>>>> I believe what you want is to check the "Resolve Issues" permission in >>>>> Jira, making sure that non-devs don't have permissions here. It means >>>>> that non-dev issue creators cannot mark an issue as 'resolved', but that >>>>> doesn't make sense anyway, because the responsibility of closing the >>>>> issue is usually with the creator anyway, so the creator in that >>>>> situation should just close it. >>>>> >>>>> On Oct 28, 2010, at 11:34 AM, Igor Vaynberg wrote: >>>>> >>>>>> yeah. a lot of it is cruft or people who report bugs setting them. >>>>>> >>>>>> i think from now on what we should do is use fix-version to construct >>>>>> a roadmap. eg dont set it unless you cant have a release without this >>>>>> in there. >>>>>> >>>>>> also i think the bigger features should have a fix version set to the >>>>>> next major version. eg we should have 1.5.0 version with >>>>>> event-handling story having fix version of both 1.5.0 and the >>>>>> milestone it was implemented in. this way it will be easier to >>>>>> construct release notes for 1.5.0. maybe we can start doing this for >>>>>> 1.6.0. >>>>>> >>>>>> in the meanwhile we should probably strip all fix-versions for open >>>>>> issues. >>>>>> >>>>>> -igor >>>>>> >>>>>> On Thu, Oct 28, 2010 at 12:25 AM, Martin Grigorov <[email protected]> >>>>>> wrote: >>>>>>> I agree. >>>>>>> The fix version should be empty until the ticket is fixed or it can be >>>>>>> set >>>>>>> to some version which would mean "this bug really needs to be fixed >>>>>>> before >>>>>>> releasing this version". >>>>>>> >>>>>>> On Thu, Oct 28, 2010 at 8:16 AM, Jeremy Thomerson >>>>>>> <[email protected] >>>>>>>> wrote: >>>>>>> >>>>>>>> Why do we have fix versions on all the 1.5 issues in JIRA that are >>>>>>>> still >>>>>>>> open? I thought our standard way of doing things was that we assigned >>>>>>>> the >>>>>>>> fixed version *when it was fixed*? >>>>>>>> >>>>>>>> When preparing to cut the 1.5-M3 release, I simply created a 1.5-M4 >>>>>>>> version >>>>>>>> and moved all open issues that have a fix version == 1.5-M3 into the >>>>>>>> new M4 >>>>>>>> version. But, I think we should remove that and assign an "affects >>>>>>>> version" >>>>>>>> instead. >>>>>>>> >>>>>>>> Thoughts? Am I misunderstanding our standard use of JIRA? >>>>>>>> >>>>>>>> -- >>>>>>>> Jeremy Thomerson >>>>>>>> http://wickettraining.com >>>>>>>> *Need a CMS for Wicket? Use Brix! http://brixcms.org* >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>> >>> >>> >> > >
