Re: [chairs] Your feedback on JIRA notifications

On Thu, Mar 1, 2018 at 10:13 AM, David Filip <david.filip@adaptcentre.ie> wrote:

Hi Chet, all,

my overall position is that I don't care how much spam a platform sends as long as the subject lines are structured enough for effective filtering.

However, I'd support creation of the terse scheme that is being discussed here.

I'd support "open" and "resolved" (not closed) to be included in terse.

The rationale being, I am notified that something is open. I care or not. But when the next notification is closed that might be too late for me to engage. Resolved (there is still applied and closed after resolved) is a good last opportunity for those who didn't engage / forgot to subscribe etc.

Cheers and thanks
dF

Dr. David Filip
===========
OASIS XLIFF OMOS TC Chair
OASIS XLIFF TC Secretary, Editor, Liaison Officer
Spokes Research Fellow
ADAPT Centre
KDEG, Trinity College Dublin
Mobile: +420-777-218-122

On Wed, Feb 28, 2018 at 3:11 PM, Chet Ensign <chet.ensign@oasis-open.org> wrote:
Hi Dave,

Thanks & great suggestions. I'm waffling back and forth on closed. I originally proposed that and then considered just open. I may go back to including closed. Most TCs use Resolved to mean that a proposed solution is in place but hasn't been finally approved yet so I would not include that in terse.

Regarding the boilerplate, I will see how much we can do there. I don't see a configuration menu that allows me to edit the text directly. Online help suggests that it requires system-level modifications. So I will need to come up with another way to make that information easily available to TC members. Because I agree with the gist of your suggestion - make it easy for people to know what to do next.

Thanks again,

/chet

On Wed, Feb 28, 2018 at 10:00 AM, Dave Lemire <dave.lemire@g2-inc.com> wrote:
Chet,

I like the basic approach, with two suggestions:

1) I think the terse scheme should also send a notice when a ticket is closed. What's the difference between "resolved" and "closed"? My suggestion might also apply to "resolved".

2) If a TC is operating with the terse scheme, the ticket-opened email should include a boilerplate reminder that there won't be any updates about the ticket's status (other than ticket closed, if you agree with my #1), and that interested members should follow the link to the ticket to opt-in for watching it in greater detail.

David P. Lemire, CISSP
OpenC2 Technical Committee Executive Secretary
OpenC2 Implementation Considerations SC Co-chair
Contractor support to NSA
Email: dave.lemire@g2-inc.com
Office: 301-575-5190 / Mobile: 240-938-9350

On Wed, Feb 28, 2018 at 9:49 AM, Chet Ensign <chet.ensign@oasis-open.org> wrote:
Thanks Kenneth. Yours was the first 'yea' vote. The result is unanimous and overwhelming to say the least. <grin>

/chet

On Tue, Feb 27, 2018 at 5:43 PM, Kenneth Bengtsson <kbengtsson@efact.pe> wrote:

Great suggestion, Chet. I’m in favor.

Best regards,

Kenneth

From: Chet Ensign <chet.ensign@oasis-open.org>
Sent: Tuesday, February 27, 2018 5:35:46 PM
To: chairs@lists.oasis-open.org; Mark Davidson
Cc: OASIS TAB; AskTheTAB@lists.oasis-open.org; Scott McGrath
Subject: [chairs] Your feedback on JIRA notifications

Chairs,

On February 9th, I contacted you to ask for your opinions on the volume of JIRA notices coming into your TC's email list. Thanks to all of you who provided feedback. This email is in response to your input.

To summarize, only a few of you indicated that the volume is a significant problem. However, most of the positive responses still conveyed that the set up is not ideal.

I reviewed the details with the TAB and as a result we are proposing the following approach.

The current JIRA TC notification scheme sends alerts to the TC list for:

Issue Created

Issue Updated

Issue Resolved

Issue Closed

Issue Commented

Issue Comment Edited

Issue Comment Deleted

Issue Reopened

Issue Deleted

Our suggestion is that I call this the TC-verbose scheme and offer, in addition, a TC-terse scheme. TC-terse would send an alert to the list when an issue is created. Those TC members who are interested in it can opt to Watch it and receive notifications for any actions. And of course anyone can go to the JIRA instance itself to see all the tickets and their state.

For TCs that want to scale back the volume of notices, I can just change their notification scheme over to TC-terse. That won't affect the issues themselves.

Please let me know your thoughts. If this seems like an option people want, I will get it implemented next week.

/chet

----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

--

/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

--

/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

chairs message