> Am 23.01.2017 um 22:47 schrieb Slide <[email protected]>: > > Ok, to summarize... > > 1) We don't want to set the assignee > 2) We do want to make sure the component(s) are correct > 3) We want to try and replicate the issue and add findings > 4) We want to close out issues that are very old with little information to > clean things up > > Is there anything I missed? >
Would it be possible to label issues in step 3 that are important and not overly complex to reproduce? I’m planning to assign several student projects to create acceptance tests for the ATH in the upcoming summer semester. The last time we tried to do this was not very effective since it took a long time to find good issues that could be transformed to an acceptance test. > Thanks for the discussion on this! > > Alex > > On Mon, Jan 23, 2017 at 2:37 PM Ullrich Hafner <[email protected] > <mailto:[email protected]>> wrote: > I would prefer to use the default Jira workflow as much as possible. So > adding a new start state would be much simpler. No other transition needs to > be changed in this case. > > > Am 21.01.2017 um 23:18 schrieb Daniel Beck <[email protected] > > <mailto:[email protected]>>: > > > > > >> On 21.01.2017, at 15:07, Baptiste Mathus <[email protected] > >> <mailto:[email protected]>> wrote: > >> > >> adding the NEW status > >> > >> Having a state to basically say: "this is issue is new, but has not been > >> reviewed, so may be invalid/incomplete/whatever for whatever reason" makes > >> sense IMO. > > > > Shouldn't we create a new "To Do" or "Confirmed" status then, to initialize > > all existing issues that aren't in progress etc. to that unverified status? > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Jenkins Developers" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected] > > <mailto:jenkinsci-dev%[email protected]>. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/jenkinsci-dev/9C189939-804F-40FB-B19F-2EF43E6EC357%40beckweb.net > > > > <https://groups.google.com/d/msgid/jenkinsci-dev/9C189939-804F-40FB-B19F-2EF43E6EC357%40beckweb.net>. > > For more options, visit https://groups.google.com/d/optout > > <https://groups.google.com/d/optout>. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:jenkinsci-dev%[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/8C8FA5DF-8CEA-4F3C-8599-F76C9C53BD22%40gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/8C8FA5DF-8CEA-4F3C-8599-F76C9C53BD22%40gmail.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdm8BYO2Cwnpq_k_AJB5VeQY%3Dc5ZV9ceBmFv%2BALX8-9Kw%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdm8BYO2Cwnpq_k_AJB5VeQY%3Dc5ZV9ceBmFv%2BALX8-9Kw%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/D65B16DD-EFEC-47F1-BC9B-4893379BEDC4%40gmail.com. For more options, visit https://groups.google.com/d/optout.
