a single global jira works for me too, as would any solution, no big
deal. It's more that I love to have my item in my task-list (jira
assigned to me).
On 12/13/2013 04:41 PM, Nick Boldt wrote:
Thanks to everyone who's tagged!
To reply to Andre's comment about jiras vs. emails (so far the only
feedback):
Task JIRAs still generate email... in fact, they generate way more
(for me, anyway) because as the opener of all the JIRAs, I get one for
each status change of: "assigned to ___" "started working",
"resolved", and "closed". So that's generally 1 or 2 JIRA emails
for
each of the 17 projects.
OTOH, when people reply to the mailing list on this thread, then
EVERYONE sees the confirmation/acknowledgement - but for people who
can tag multiple projects, it reduces their overhead from 3 x 2 JIRAs
down to 1 single email.
Replying to me directly would produce the same confirmation response
but w/o the list-spam & dozens of people hitting their delete keys. :)
What about having *1 JIRA for all project tagging*, and everyone can
just comment there when done, without having to take ownership of the
JIRA? That would provide
tracking/confirmation/auditing/accountability, and also reduce the
amount of mail generated.
As a project lead, you'd still get everyone's "___ is tagged" emails
as generated by JIRA, but then the whole world wouldn't also see their
spammy goodness in jbosstools-dev@.
WDYT?
N
On 12/13/2013 08:25 AM, Andr� Dietisheim wrote:
> Done for openshift.
>
> btw. I personally prefer the jira approach, keeps jira as the single
> task-listing authority, no mail-spams "Yes, done here".
>
> On 12/12/2013 11:00 PM, Nick Boldt wrote:
>> Project leads, please tag your projects!
>>
>> co jbosstools-4.1.1.x
>> git tag jbosstools-4.1.1.Final
>> git push origin jbosstools-4.1.1.Final
>>
>>
>> (This single email replaces 17 Task JIRAs. If you prefer this approach,
>> let me know. If you prefer JIRAs, let me know that too.)
>>
>