> On 7. Sep 2019, at 03:52, Jesse Glick wrote:
>
> I tried this, but it does not do what I need: it just sends, say, a
> daily list of all issues matching that filter. To replace the
> notification function of default assignee, I would want something that
> only send me _changes_ in issues
On Thu, Sep 5, 2019 at 7:01 PM Oleg Nenashev wrote:
> create a filter (or to use a public one), go to "Details" and then to
> subscribe to notifications there.
I tried this, but it does not do what I need: it just sends, say, a
daily list of all issues matching that filter. To replace the
Filterers can be saved and shared, and so a default search could be setup
with
https://confluence.atlassian.com/jira063/advanced-searching-functions-683542527.html#AdvancedSearchingFunctions-componentsLeadByUser()
and then any custom requirements could be forked and tweaked per user.
On Fri.,
I totally agree with the general opinion that an issue should only be assigned
to someone if that person is effectively ready to work on it otherwise it just
bring confusion about either the assignee will effectively works on it or not.
And I also understand that people use default assignee to
My first thought was that I would like to keep the default assignee - but after
reading all the comments, I have to agree, that my only reason for this is so
that I get notified by new issues. Although Oleg shoed it is possible to create
a filter and get notified about this things, It seems
Making it an optional field in the HOSTING report seems to be a good
compromise, so +1 from me for such a change.
(I understand that developers do not want to be assignee for issues they are
never going to fix. On the other hands, for a user that reports an issue it is
somewhat disappointing
On Thu, Sep 5, 2019 at 2:36 PM Gavin wrote:
> Does jira have a concept of auto watch like GitHub does? So an issue could
> still notify people but not be claimed?
Good question. That would be very useful.
--
You received this message because you are subscribed to the Google Groups
"Jenkins
Does jira have a concept of auto watch like GitHub does? So an issue could
still notify people but not be claimed?
On Thu., Sep. 5, 2019, 11:35 a.m. Matt Sicker,
wrote:
> That makes tons of sense to me. You should only assign tickets to
> yourself that you're currently working on or at least
That makes tons of sense to me. You should only assign tickets to
yourself that you're currently working on or at least intend to work
on in the near future.
On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus wrote:
>
> I fully agree with Jesse's take. IMO for most plugins where the maintainer is
>
I fully agree with Jesse's take. IMO for most plugins where the maintainer
is not going to have time to jump on new reports right away, this sends a
wrong message that issues will be analyzed and fixed by the assignee.
This sends a second bad message: that an issue being already assigned, this
is
10 matches
Mail list logo
