“active” states.
BR,
Maurice
> -Original Message-
> From: Development On Behalf Of
> Edward Welbourne
> Sent: Thursday, February 20, 2020 2:37 PM
> To: Tobias Hunger
> Cc: development@qt-project.org
> Subject: Re: [Development] Proposal: more Jira states to track st
On Mon, 2020-02-17 at 09:13 +, Edward Welbourne wrote:
>> We currently have an "In Progress" state. In practice when I work on an
>> issue, I initially do the work, then put that up for review; the review
>> phase takes up fragments of my time for a while, unlike the main work
>> phase, which
On 17/02/2020 10:13, Edward Welbourne wrote:
>> We currently have an "In Progress" state. In practice when I work on
>> an issue, I initially do the work, then put that up for review; the
>> review phase takes up fragments of my time for a while, unlike the
>> main work phase, which is closer to f
TL;DR: I struggle to find any substance in André's objections.
Meanwhile, I'd really like to hear from folk more familiar with Jira:
* Would a new state actually make it possible to show a useful
distinction, on Jira's scrum boards, between tasks in progress and
those in review ? Or is Jira's
> On 20 Feb 2020, at 00:08, André Pönitz wrote:
> On Wed, Feb 19, 2020 at 10:43:17AM +, Volker Hilsheimer wrote:
>> Even when doing development (as opposed to the pointy-haired work), I
>> benefit from having tools that help me to maintain a work-in-progress
>> limit, that allow me to see what
On Mon, 2020-02-17 at 09:13 +, Edward Welbourne wrote:
> We currently have an "In Progress" state. In practice when I work on an
> issue, I initially do the work, then put that up for review; the review
> phase takes up fragments of my time for a while, unlike the main work
> phase, which is c
Hi,
On 17/02/2020 10:13, Edward Welbourne wrote:
> Hi all,
>
> We currently have an "In Progress" state. In practice when I work on an
> issue, I initially do the work, then put that up for review; the review
> phase takes up fragments of my time for a while, unlike the main work
> phase, which
On Wed, Feb 19, 2020 at 10:43:17AM +, Volker Hilsheimer wrote:
> Even when doing development (as opposed to the pointy-haired work), I
> benefit from having tools that help me to maintain a work-in-progress
> limit, that allow me to see what state the work someone else is doing
> is in (because
On Wed, Feb 19, 2020 at 09:45:48AM +, Edward Welbourne wrote:
> On Tue, Feb 18, 2020 at 01:11:29PM +1000, Lorn Potter wrote:
> >> Stepping through the interim steps is not a requirement, so it is not that
> >> much difference to go from Reported->In Progress to Reported->In Review,
> >> really.
> On 19 Feb 2020, at 10:45, Edward Welbourne wrote:
>
What's the harm in leaving the task in In Progress state while it's being
reviewed?
>>>
>>> There is no harm, but being able to better distinguish the main development
>>> phase of a large task from the review stage would benefit th
On Tue, Feb 18, 2020 at 01:11:29PM +1000, Lorn Potter wrote:
>> Stepping through the interim steps is not a requirement, so it is not that
>> much difference to go from Reported->In Progress to Reported->In Review,
>> really.
>>
>> So the list you have to select from has one more entry to choose fr
On Tue, Feb 18, 2020 at 01:11:29PM +1000, Lorn Potter wrote:
> On 18/2/20 6:03 AM, Thiago Macieira wrote:
> > I'm with Alexandru here: all ideas to have more states in JIRA start with a
> > good intentions, but eventually people stop using them and just transition
> > through all stages in one go w
On Mon, Feb 17, 2020 at 09:13:17AM +, Edward Welbourne wrote:
> When my team is planning sprints, our scrum master wants to know what
> tasks I'll be working on, and what counts as "Done" for each of them.
> Having a separate state for "In Review", distinct from "In Progress",
> would let us di
On 18/2/20 6:03 AM, Thiago Macieira wrote:
>> I'm with Alexandru here:
I confess I'd understood Alexandru as saying he'd wanted similar in the
past but not been allowed it. Perhaps I misunderstood ...
>> all ideas to have more states in JIRA start with a good intentions,
>> but eventually people
On 18/2/20 6:03 AM, Thiago Macieira wrote:
I'm with Alexandru here: all ideas to have more states in JIRA start with a
good intentions, but eventually people stop using them and just transition
through all stages in one go when they've finished the work. For example,
people realise they've neve
On 17/2/20 7:13 PM, Edward Welbourne wrote:
So I'd like to modify our Jira work-flows to include a distinct "In
Review" state for when I've completed the main work and am either
waiting for review or responding to reviewers' comments. Of course, if
those comments prompt me to go back and start
On Monday, 17 February 2020 01:20:43 PST Alexandru Croitor wrote:
> Last time I brought this up, I was told that it would complicated the states
> / transitions, and was deemed won't fix.
>
> I hope you have more luck.
I'm with Alexandru here: all ideas to have more states in JIRA start with a
g
Sounds like a good idea.
It also would be nice to integrate this change with gerrit somehow. For
example, if you push non-WIP changes and add reviewers, an associated
task should be moved to "In Review" state automatically.
On 2/17/20 10:13 AM, Edward Welbourne wrote:
> Hi all,
>
> We currently
Hi,
Last time I brought this up, I was told that it would complicated the states /
transitions, and was deemed won't fix.
I hope you have more luck.
> On 17. Feb 2020, at 10:13, Edward Welbourne wrote:
>
> Hi all,
>
> We currently have an "In Progress" state. In practice when I work on an
>
Hi all,
We currently have an "In Progress" state. In practice when I work on an
issue, I initially do the work, then put that up for review; the review
phase takes up fragments of my time for a while, unlike the main work
phase, which is closer to full-time. I have more control over (and a
bette
20 matches
Mail list logo
