On the other had, the (single) Workflow has not been changed since 2016-07, and there are arcs from All to each of the states.
Raised to blocker. This new behavior is affecting pretty much every open JIRA ticket across all projects as far as I can see.
mark this as dup to INFRA-200.
This is different. All options to change workflow are now gone. And this appears to have happened over this weekend. Only an 'open' button remains.
I will relate the two issues but I think there is no duplicate.
hrm.. that seems the same as what I've reported at INFRA-200... > only 'open'
we had some change on group definition to switch entirely into LDAP recently, but not sure it relates or not.
Ok, perhaps you are correct - it's strange that it is now happening across all projects though.
I just ran the integrity checker BTW and it shows no problems. So it could be a user privilege problem. Will try re-indexing first.
Looking at the transitions under admin, only users in group jira-developers can execute this transition.
The only user in that group is pfs-jira-admin jira@pfs.ipmu.jp
.
Adding myself explicitly to the jira-developers role seems to fix the problem, but for me alone. We need to find a general solution of restoring all PFS developers to this role.
As shimono mentions before, there has been some changes made recently to the jira-developers group with respect to LDAP. It does not make sense to me why the only user is jira@pfs.ipmu.jp . shimono: can you check that this is correct?
As it is important for developers to make transitions, I will in the next few hours (if there are no objections) temporarily add the group jira-ldap-users to the jira-developers list.
This would mean that pretty much all users will have access to all transitions. But I believe we can trust people during this temporary period. And I believe any minor abuse is better than to lock transitions from developers.
jira-(administrators|developers|users) are built in group wihtin JIRA application, jira-ldap-* are defined in LDAP for SSO. pfs-jira-admin is the sole admin account in the JIRA local dictionary created at the first installation but not from LDAP - so this account should be in all
of built in groups (if no there is no control on issue happened).
to prevent misoperation, especially to perform messy additional configuration at external from LDAP, we set jira-ldap-* as default group(s) for accounts from LDAP.
Having pfs-jira-admin in the jira-developers group is fine.
But it seems that non of the jira-ldap-* users are being propagated to the jira-developers group.
I can add them all explicitly, but there does seem to be an LDAP issue.
Because it is not possible to have one JIRA group as a member of another, I have added, temporarily, all the individual members of the jira-ldap-users group to the jira-developers group.
This change should be reverted as soon as a long-term solution is understood and implemented.
Priority dropped from blocker to major. I suggest that this issue remains open until the aforementioned long term solution is found,