Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-swt-dev] Thought: Followup / Due date in Bugzilla
Thank you for sharing that idea.

That works for gerrit followups. But what about the general "followup later" situation?

Example use cases:
- We want to postpone work on a bug till a code-freeze is over in XYZ days. (this would benefit from specific date).
- A user says that he will test the patch XYZ days. We want to followup in XYZ + 3 days to check if the user actually tested a patch.
- We want to postpone work on a bug  for XYZ days until a patch has been 'tested by community' and if no complaints then backport it to previous milestones.
- We are waiting for GTK folks to fix an underlying GTK bug, but would like to followup on GTK people in XYZ days to check if they made progress on the bug.
  (XYZ can be very big or small in such situations).
- We want to followup on a related bug or a child bug of the current bug, to see if it can be accelerated.
- We want to followup a gerrit patch submission in XYZ days (maybe urgent in which case XYZ is small, or not urgent in which case XYZ is big).
.... etc...

(as listed above)
- We want to followup with reporter for additional information in XYZ days.

I can't think of a keyword/field match query that incorporates "XYZ days" where XYZ is a variable number.
As such, for all of the above I have to make a note of the bug in an external todo system.

Does anyone have any other ideas on how to deal with the "generic followup" situation with dates without resorting to external tools?

Also I'm curious, would there be reasons why not to introduce some "followup" datetime field besides added clutter?

Thank you.

---
Leo Ufimtsev
Software Engineer, Eclipse team.
Toronto, Canada

Red Hat, Inc.

On Tue, Nov 29, 2016 at 12:08 PM, Stephan Herrmann <stephan.herrmann@xxxxxxxxx> wrote:
To check status of submitted gerrits I typically use
        See also   contains the string  git.eclipse.org/r
combined with criteria like unresolved etc.

Stephan

On 11/29/2016 06:04 PM, Leo Ufimtsev wrote:
Hello Dani,

I just bumped into another situation where "followup" is needed.

I submitted a patch for review and I'd like to followup on the patch being merged. If it's not reviewed (ex the reviewer is on
holiday), then I could request another contributor to review the patch.
In such case the 'needinfo' keyword doesn't quite work.

Does anyone have any suggestion for such a situation? (I couldn't find a suitable keyword).

Thank you

Leo






---
Leo Ufimtsev
Software Engineer, Eclipse team.
Toronto, Canada

Red Hat, Inc.
Leonidas@xxxxxxxxxx <mailto:Leonidas@xxxxxxxxxx> | http://DeveloperBlog.RedHat.com/ <http://developerblog.redhat.com/>


On Tue, Nov 29, 2016 at 3:19 AM, Daniel Megert <daniel_megert@xxxxxxxxxx <mailto:daniel_megert@xxxxxx.com>> wrote:

    Hi Leo

    Whenever we ask a question we add the 'needinfo' keyword. We can then query for bugs with that keyword and close those who
    didn't change for a while.

    There's also service running that pings on our bugs every year and adds "stalebug" to the Whiteboard field.

    Dani



     From:        Leo Ufimtsev <lufimtse@xxxxxxxxxx <mailto:lufimtse@xxxxxxxxxx>>
    To:        "Eclipse Platform SWT component developers list." <platform-swt-dev@xxxxxxxxxxx <mailto:platform-swt-dev@eclipse.org>>
    Date:        28.11.2016 21:14
    Subject:        [platform-swt-dev] Thought: Followup / Due date in Bugzilla
     Sent by:        platform-swt-dev-bounces@eclipse.org <mailto:platform-swt-dev-bounces@xxxxxxxxxxx>
    ------------------------------------------------------------------------------------------------------------------------------------



    Hello fellow SWT developers,

    I'm just playing around with a thought (before submitting a bug ticket..) and would like to hear your thoughts.

    In our bugzilla instance, there is no way (afaik) to schedule a followup on a bug *via the web-interface*.

    Use case: When user submits a bug and we ask a user a question, if there is no reply within 2 weeks, I would like to close the
    ticket.

    I know Mylyn can do this, but when some other developer asks a question to some user, we do not see their private Mylyn data and
    some bug tickets get forgotten in time. Also, although I like to use Mylyn, not everyone uses it.


     *One solution to this:*

    In the Red Hat bugzilla, there is a 'Deadline' date field:


    And with Bugzilla query, you can query relative dates.
    So for example to find tasks that are past their deadline:

     See: _http://docs.devzing.com/bugzilla-searching-with-relative-dates/_
    <http://docs.devzing.com/bugzilla-searching-with-relative-dates/>

    My suggestion is that we request our Bugzilla admins to add a "Followup/Due" date datetime field. (or just "Followup" datetime
    field).

    Thoughts?

    ---
    Leo Ufimtsev
    Software Engineer, Eclipse team.
    Toronto, Canada

    Red Hat, Inc.
     _Leonidas@redhat.com_ <mailto:Leonidas@xxxxxxxxxx>| _http://DeveloperBlog.RedHat.com/_ <http://developerblog.redhat.com/>

    [attachment "Selection_295.png" deleted by Daniel Megert/Zurich/IBM] [attachment "Selection_294.png" deleted by Daniel
    Megert/Zurich/IBM] _______________________________________________
    platform-swt-dev mailing list
     platform-swt-dev@xxxxxxxxxxx <mailto:platform-swt-dev@eclipse.org>
    To change your delivery options, retrieve your password, or unsubscribe from this list, visit
     https://dev.eclipse.org/mailman/listinfo/platform-swt-dev <https://dev.eclipse.org/mailman/listinfo/platform-swt-dev>



    _______________________________________________
    platform-swt-dev mailing list
    platform-swt-dev@xxxxxxxxxxx <mailto:platform-swt-dev@eclipse.org>
    To change your delivery options, retrieve your password, or unsubscribe from this list, visit
     https://dev.eclipse.org/mailman/listinfo/platform-swt-dev <https://dev.eclipse.org/mailman/listinfo/platform-swt-dev>




_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev


_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev

Back to the top