You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Joachim Rohde <ma...@joachimrohde.com> on 2021/02/05 14:03:41 UTC
How are resolved but not yet closed JIRA tickets handled?
Hi everyone
Just got short beginner question: I've just created my first JIRA ticket
for NetBeans (NETBEANS-5335). Before I created the ticket I was
searching JIRA if there was already a ticket. Even though I couldn't
find any I found some other tickets that were still in status "resolved"
but already had a "Fix Version" pre 12.3 and the last update was
sometimes already half a year ago (e.g. NETBEANS-2333, NETBEANS-3428,
NETBEANS-4474, NETBEANS-4507). So I was asking myself how this is
handled within the NetBeans project? Are you waiting till the ticket
creator closes the ticket? Is there a recurring clean-up? Should I ping
the creator if I see such a ticket? Or mentioning it here on the mailing
list so someone with the right rights can close it? What's best practice
here?
Have a nice weekend,
Joachim
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: How are resolved but not yet closed JIRA tickets handled?
Posted by Tomáš Procházka <ka...@razdva.cz>.
OK, hints give some ideas.
- "Resolve Issue" indicates that Assignee resolved the issue and
Reporter can approve suggested resolution. At this moment also Fix
Version should be set.
- "Close Issue" directly closes issue, no further reaction is expected
and it's not possible to change properties of the issue (like Fix
Version or Component).
I went through all resolved issues and closed them. There were 514 of
them so sorry for the mail flood.
Tom
On 05. 02. 21 17:04, Eric Bresie wrote:
> In my experience with JIRA, some of this depends on the "workflow", state
> transitioned rules, and role/permissions for given JIRA project/user.
>
> There are two similar fields "Status" and a "Resolution" field. Maybe
> getting confused around this. For a random ticket I see the following:
>
> Status:OPEN
> Resolution:Unresolved
>
>
> I believe the links at the top may help transition the "Status" between
> states. Same random ticket I see
>
> - Start Progress
> - Resolve Issue
> - Close Issue
>
> The links available may be different depending on the current state.
>
> Assume the "Resolve Issue" may result in it being "resolved" but not yet
> closed. Assume the "Close Issue" may be needed.
>
> Is there any "JIRA Usage" documentation (for Apache or Team) maybe on an
> applicable documentation page somewhere that spells this out?
>
> On Fri, Feb 5, 2021 at 9:43 AM Tomáš Procházka <ka...@razdva.cz> wrote:
>
>> Hi,
>>
>> I think once the ticket is resolved it stays in this state. It
>> disappears from open tickets and resolution status is no more "Unresolved".
>>
>> When I went through tickets last time I used Resolve or Close button.
>> Never closed resolved issue.
>>
>> Regards,
>>
>> Tom
>>
>> On 05. 02. 21 15:03, Joachim Rohde wrote:
>>> Hi everyone
>>>
>>> Just got short beginner question: I've just created my first JIRA ticket
>>> for NetBeans (NETBEANS-5335). Before I created the ticket I was
>>> searching JIRA if there was already a ticket. Even though I couldn't
>>> find any I found some other tickets that were still in status "resolved"
>>> but already had a "Fix Version" pre 12.3 and the last update was
>>> sometimes already half a year ago (e.g. NETBEANS-2333, NETBEANS-3428,
>>> NETBEANS-4474, NETBEANS-4507). So I was asking myself how this is
>>> handled within the NetBeans project? Are you waiting till the ticket
>>> creator closes the ticket? Is there a recurring clean-up? Should I ping
>>> the creator if I see such a ticket? Or mentioning it here on the mailing
>>> list so someone with the right rights can close it? What's best practice
>>> here?
>>>
>>> Have a nice weekend,
>>> Joachim
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
>>> For additional commands, e-mail: dev-help@netbeans.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
>> For additional commands, e-mail: dev-help@netbeans.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: How are resolved but not yet closed JIRA tickets handled?
Posted by Eric Bresie <eb...@gmail.com>.
In my experience with JIRA, some of this depends on the "workflow", state
transitioned rules, and role/permissions for given JIRA project/user.
There are two similar fields "Status" and a "Resolution" field. Maybe
getting confused around this. For a random ticket I see the following:
Status:OPEN
Resolution:Unresolved
I believe the links at the top may help transition the "Status" between
states. Same random ticket I see
- Start Progress
- Resolve Issue
- Close Issue
The links available may be different depending on the current state.
Assume the "Resolve Issue" may result in it being "resolved" but not yet
closed. Assume the "Close Issue" may be needed.
Is there any "JIRA Usage" documentation (for Apache or Team) maybe on an
applicable documentation page somewhere that spells this out?
On Fri, Feb 5, 2021 at 9:43 AM Tomáš Procházka <ka...@razdva.cz> wrote:
> Hi,
>
> I think once the ticket is resolved it stays in this state. It
> disappears from open tickets and resolution status is no more "Unresolved".
>
> When I went through tickets last time I used Resolve or Close button.
> Never closed resolved issue.
>
> Regards,
>
> Tom
>
> On 05. 02. 21 15:03, Joachim Rohde wrote:
> > Hi everyone
> >
> > Just got short beginner question: I've just created my first JIRA ticket
> > for NetBeans (NETBEANS-5335). Before I created the ticket I was
> > searching JIRA if there was already a ticket. Even though I couldn't
> > find any I found some other tickets that were still in status "resolved"
> > but already had a "Fix Version" pre 12.3 and the last update was
> > sometimes already half a year ago (e.g. NETBEANS-2333, NETBEANS-3428,
> > NETBEANS-4474, NETBEANS-4507). So I was asking myself how this is
> > handled within the NetBeans project? Are you waiting till the ticket
> > creator closes the ticket? Is there a recurring clean-up? Should I ping
> > the creator if I see such a ticket? Or mentioning it here on the mailing
> > list so someone with the right rights can close it? What's best practice
> > here?
> >
> > Have a nice weekend,
> > Joachim
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: How are resolved but not yet closed JIRA tickets handled?
Posted by Tomáš Procházka <ka...@razdva.cz>.
Hi,
I think once the ticket is resolved it stays in this state. It
disappears from open tickets and resolution status is no more "Unresolved".
When I went through tickets last time I used Resolve or Close button.
Never closed resolved issue.
Regards,
Tom
On 05. 02. 21 15:03, Joachim Rohde wrote:
> Hi everyone
>
> Just got short beginner question: I've just created my first JIRA ticket
> for NetBeans (NETBEANS-5335). Before I created the ticket I was
> searching JIRA if there was already a ticket. Even though I couldn't
> find any I found some other tickets that were still in status "resolved"
> but already had a "Fix Version" pre 12.3 and the last update was
> sometimes already half a year ago (e.g. NETBEANS-2333, NETBEANS-3428,
> NETBEANS-4474, NETBEANS-4507). So I was asking myself how this is
> handled within the NetBeans project? Are you waiting till the ticket
> creator closes the ticket? Is there a recurring clean-up? Should I ping
> the creator if I see such a ticket? Or mentioning it here on the mailing
> list so someone with the right rights can close it? What's best practice
> here?
>
> Have a nice weekend,
> Joachim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: How are resolved but not yet closed JIRA tickets handled?
Posted by Tomáš Procházka <ka...@razdva.cz>.
This is good opportunity for volunteers who want to participate but are
afraid of Java/NetBeans internals.
JIRA contains a lot of bug reports and some of them are incomplete,
reported for older versions or have assigned wrong component. Some of
the are kind of fire-and-forget without any reaction to additional
questions.
Any NetBeans user can check if it is clear from description what the
issue or feature request is about. Bugs for older version need to be
verified if they can be reproduced.
Here is my suggestion for website:
https://github.com/apache/netbeans-website/pull/514
Tom
On 05. 02. 21 16:00, Neil C Smith wrote:
> On Fri, 5 Feb 2021 at 14:52, Eric Bresie <eb...@gmail.com> wrote:
>> Who is responsible for the ticket? Once included in a release should these
>> tickets be closed by the user, by the release manager, by some JIRA admin
>> with "close permissions", some member of a "CCB/Admin" group with
>> applicable permissions?
> By anyone in this community with permissions to do so! :-)
>
> When RM'ing I try to keep an eye on and close things I know have been
> merged. But it should definitely not be solely the RM's job ...
> please. We need to get a handle on how we use JIRA, because IMO it's
> getting more and more unwieldy and out of sync with actual
> development. It would be good to look at automating closing issues
> with tagged PRs merging too.
>
> Best wishes,
>
> Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: How are resolved but not yet closed JIRA tickets handled?
Posted by Neil C Smith <ne...@apache.org>.
On Fri, 5 Feb 2021 at 14:52, Eric Bresie <eb...@gmail.com> wrote:
> Who is responsible for the ticket? Once included in a release should these
> tickets be closed by the user, by the release manager, by some JIRA admin
> with "close permissions", some member of a "CCB/Admin" group with
> applicable permissions?
By anyone in this community with permissions to do so! :-)
When RM'ing I try to keep an eye on and close things I know have been
merged. But it should definitely not be solely the RM's job ...
please. We need to get a handle on how we use JIRA, because IMO it's
getting more and more unwieldy and out of sync with actual
development. It would be good to look at automating closing issues
with tagged PRs merging too.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: How are resolved but not yet closed JIRA tickets handled?
Posted by Eric Bresie <eb...@gmail.com>.
I had had some questions around this following 12.2 release (1) but never
got any follow up on it.
Who is responsible for the ticket? Once included in a release should these
tickets be closed by the user, by the release manager, by some JIRA admin
with "close permissions", some member of a "CCB/Admin" group with
applicable permissions?
Would another suggestion provide a list of tickets that may need to be
closed out and provide to the list and then they can be asset and closed
out as needed?
Reference:
(1)
https://lists.apache.org/thread.html/r29c7c17bbb3cc98c640f07bca62d8adaf43f703d1c6d61b4607d91d4%40%3Cdev.netbeans.apache.org%3E
Eric Bresie
ebresie@gmail.com
On Fri, Feb 5, 2021 at 8:19 AM Joachim Rohde <ma...@joachimrohde.com>
wrote:
> Hi everyone
>
> Just got short beginner question: I've just created my first JIRA ticket
> for NetBeans (NETBEANS-5335). Before I created the ticket I was
> searching JIRA if there was already a ticket. Even though I couldn't
> find any I found some other tickets that were still in status "resolved"
> but already had a "Fix Version" pre 12.3 and the last update was
> sometimes already half a year ago (e.g. NETBEANS-2333, NETBEANS-3428,
> NETBEANS-4474, NETBEANS-4507). So I was asking myself how this is
> handled within the NetBeans project? Are you waiting till the ticket
> creator closes the ticket? Is there a recurring clean-up? Should I ping
> the creator if I see such a ticket? Or mentioning it here on the mailing
> list so someone with the right rights can close it? What's best practice
> here?
>
> Have a nice weekend,
> Joachim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>