In case your Jira user name differed from your OASIS user name: you can (have to) log in to Jira now with your OASIS user name.
You might want to reassign Jira tickets to your new Jira user name. This can be done with bulk actions.
From: Chet Ensign [mailto:chet.ensign@oasis-open.org]
Sent: Freitag, 31. Juli 2015 16:58
To: William Cox
Cc: chairs@lists.oasis-open.org; tc-admin@oasis-open.org
Subject: [chairs] Re: [TC Admin] Re: [chairs] Upcoming improvement to OASIS JIRA
Hey, good morning Bill. Excellent questions.
On Fri, Jul 31, 2015 at 9:49 AM, William Cox <wtcox@coxsoftwarearchitects.com> wrote:
I really appreciate having a consistent ID space across the various OASIS-supported technologies.
Yes, this has been needed for a long time.
I have a couple of questions about the transition:
(1) Will the "old IDs" will remain and can be searched for? This is important because the history of TC discussions is in part in Jira . My recollection is that no-longer-members can be searched for and bulk changed to current members, based on finding issues
owned by ex-TC members.
Yes they will. The assignments will remain on the tickets even though the ID itself is deactivated. So I believe that you can search for them and then do a bulk reassignment.
(2) It's not clear from your email what Jira roles will be assigned. Are all of the roles going to be automatically set? Different TCs seem to have different approaches - one TC I'm in does not give developer/editor permissions to all members, others do. This
might mean that a TC member cannot open an issue. (Ones I chair tend to give all rights except admin and chair to all TC members)
I'm not aware of any TCs that have specifically asked to restrict abilities to just the chairs. My intention is to do what I do today - assign every role to the members of the TC. If a particular TC wants me to dial that back to just the
chairs, I'll handle that individually.
(3) One of the reasons for the separate management was that the form of IDs in Jira was different from those in Kavi - e.g. user names in Jira must start with a lower case letter. Sounds like that Jira restriction has been eased.
I'm not sure. I'd have to check with Jesse on that. It may be the case that all letters have to be lower case. I'll check.
Thanks!
bill
--
On 7/29/15 6:09 PM, Chet Ensign wrote:
OASIS chairs and members,
This coming weekend, we are migrating OASIS's JIRA authentication over so that it uses Kavi's LDAP directory to control access and log ins.
This is good news because it means that you will no longer have to work through me to get TC members added to your JIRA project. Access will work just like it does for TC wikis and SVN instances: TC members
automatically gain access and, when people leave your TC, their access will be closed down.
When you return to work on Monday, August 3rd, you will log in to JIRA with your OASIS credentials to have full access.
Some of you are in JIRA today under outdated logins. Those logins will no longer work. You'll log in now with your current OASIS user name and password.
One possible complication may arise if you were assigned to issues under an old ID. In those cases, you will need to go to those issues and reassign them to yourself under your new login. If you have any difficulty
making the reassignment or this proves to be especially onerous, please contact me so that I can help resolve it.
This will be a quality of life improvement for all of us - certainly for me. You will no longer need to guess whether your roster is up to date on JIRA nor will I be a bottleneck to your TCs work.
Please let me know if you have any questions or encounter any problems.
Best,
--
/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
|