gt;>>>>>>>>
>>>>>>>>>>>>>>> +1 for automation.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Regarding #4, wh
re more
>>>>>>>>>>>>>> information
>>>>>>>>>>>>>> from the reporter?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Unfortunately it would require a human
el. Triage should
>>>>>>>>>>>>> happen
>>>>>>>>>>>>> regularly anyways, ideally even periodically for old issues,
>>>>>>>>>>>>> though this
>>>>>&
t;>> Even with automation, manual triaging would be a valuable
>>>>>>>>>>> action. If the automation can reduce the backlog for manual
>>>>>>>>>>> reviewers,
>>>>>>>>>>> doing manual tria
t;>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Regarding #5 & #6, having some SLO for P0/P1 issues for both
>>>>>>>>>>> updates and closures would be helpful in setting expectations. A
>>>>
d be neat if it could ping
>>>>>>>>>> the
>>>>>>>>>> assignee directly. What group would be victims for the auto-assigner?
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I agre
gt; I agree with this. Email, or a dashboard would work equally well.
>>>>>>>> (We need to first agree on SLOs though.)
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 2020/04/
t;>>>>>> >
>>>>>>>> > I like the idea of using automation to help tame the backlog of
>>>>>>>> jiras, but
>>>>>>>> > I worry that 4 could lead to a bad experience for users. Say they
>>>>
le a
>>>>>>> > jira and maybe get it assigned, and then watch as it bounces all
>>>>>>> the way
>>>>>>> > down to closed as obsolete because it was ignored.
>>>>>>> > The status quo (the bug just gets ignored anyway
>>>>>> > down to closed as obsolete because it was ignored.
>>>>>> > The status quo (the bug just gets ignored anyway) isn't great, but
>>>>>> at least
>>>>>> > the user doesn't have automation working ag
>>>>> > the user doesn't have automation working against them.
>>>>> >
>>>>> > Is there something else we can do to make sure these bugs get
>>>>> attention?
>>>>> >
>>>>> > Brian
>&
>>>> > Brian
>>>> >
>>>> >
>>>> > On Wed, Apr 29, 2020 at 10:00 AM Robert Bradshaw >>> >
>>>> > wrote:
>>>> >
>>>> > > +1 to more automation.
>>>> > >
>> > >
>>> > > I'm in favor of all but 4, I think it's quite common for issues to be
>>> > > noticed but not worked on for 60+ days. Most of the time when a
>>> developer
>>> > > files an issue they either (1) are working o
t; filing it away because it's something they're not working on, but
>> should
>> > > get fixed. (Case in point, beginner issues that are not urgent but
>> nice to
>> > > have.) What we could do however is lower the priority after a set
>> amount of
>> >
mething they're not working on, but
> should
> > > get fixed. (Case in point, beginner issues that are not urgent but
> nice to
> > > have.) What we could do however is lower the priority after a set
> amount of
> > > time. (I suppose issues are a mix of bloc
mix of blockers and backlog, and the two
> > have very different characteristics.)
> >
> > On Wed, Apr 29, 2020 at 9:38 AM Kenneth Knowles wrote:
> >
> >> Hi all,
> >>
> >> A while ago [1], we discussed using "Automation for Jira" to im
he two
> have very different characteristics.)
>
> On Wed, Apr 29, 2020 at 9:38 AM Kenneth Knowles wrote:
>
>> Hi all,
>>
>> A while ago [1], we discussed using "Automation for Jira" to improve
>> triage and backlog processing (I spend a lot of my time
d, Apr 29, 2020 at 9:38 AM Kenneth Knowles wrote:
> Hi all,
>
> A while ago [1], we discussed using "Automation for Jira" to improve
> triage and backlog processing (I spend a lot of my time on this). Due to
> some friction [2] [3] back then, I did not finish it.
>
&
Hi all,
A while ago [1], we discussed using "Automation for Jira" to improve triage
and backlog processing (I spend a lot of my time on this). Due to some
friction [2] [3] back then, I did not finish it.
Now, I just happened to check and I do have the ability to create rules
direct
19 matches
Mail list logo
