https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INFRA-204 Software Development Infrastructure <p>The Workflow button on Issue pages is now just an <tt>Open</tt> button, and not a pulldown. I think this is a Workflow issue and not a screen issue, since my personal Kanban does not allow me to move issues from <tt>Backlog</tt> to <tt>In Progress</tt>. The error is: <tt>We can't move this issue to In Progress. Check if your workflow allows this transition and if all transition conditions are met.</tt></p> INFRA-204

Current workflow does not allow transitions from Open

Bug Major Open Unresolved yuki.moritani cloomis Mon, 4 Jun 2018 12:50:15 +0000 Thu, 4 Apr 2019 15:11:18 +0000 0 3 <p>On the other had, the (single) Workflow has not been changed since 2016-07, and there are arcs from <tt>All</tt> to each of the states. </p> <p>Raised to blocker. This new behavior is affecting pretty much every open JIRA ticket across all projects as far as I can see.</p> <p>mark this as dup to <a href="https://pfspipe.ipmu.jp/jira/browse/INFRA-200" title="cannot mark ticket as in review or done" class="issue-link" data-issue-key="INFRA-200"><del>INFRA-200</del></a>.</p> <p>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. </p> <p>I will relate the two issues but I think there is no duplicate.</p> <p>hrm.. that seems the same as what I've reported at <a href="https://pfspipe.ipmu.jp/jira/browse/INFRA-200" title="cannot mark ticket as in review or done" class="issue-link" data-issue-key="INFRA-200"><del>INFRA-200</del></a>... &gt; only 'open'<br/> we had some change on group definition to switch entirely into LDAP recently, but not sure it relates or not.</p> <p>Ok, perhaps you are correct - it's strange that it is now happening across all projects though.</p> <p>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.</p> <p>Looking at the transitions under admin, only users in group <b>jira-developers</b> can execute this transition.</p> <p>The only user in that group is pfs-jira-admin  <span class="nobr"><a href="mailto:jira@pfs.ipmu.jp" class="external-link" rel="nofollow">jira@pfs.ipmu.jp^{<img class="rendericon" src="https://pfspipe.ipmu.jp/jira/images/icons/mail_small.gif" height="12" width="13" align="absmiddle" alt="" border="0"/>}</a></span> . </p> <p>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.</p> <p>As <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=atsushi.shimono" class="user-hover" rel="atsushi.shimono">shimono</a> 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 <span class="nobr"><a href="mailto:jira@pfs.ipmu.jp" class="external-link" rel="nofollow">jira@pfs.ipmu.jp^{<img class="rendericon" src="https://pfspipe.ipmu.jp/jira/images/icons/mail_small.gif" height="12" width="13" align="absmiddle" alt="" border="0"/>}</a></span> . <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=atsushi.shimono" class="user-hover" rel="atsushi.shimono">shimono</a>: can you check that this is correct?</p> <p>As it is important for developers to make transitions, I will in the next few hours (if there are no objections) <b>temporarily</b> add the group <a href="https://pfspipe.ipmu.jp/jira/projects/INFRA/ViewGroup.jspa?atl_token=B3PR-B5SM-ORV9-JTGI%7C073d6c8a963184a9907088a88c7d46f11d9d1364%7Clin&amp;name=jira-ldap-users" class="external-link" rel="nofollow">jira-ldap-users</a> to the jira-developers list. </p> <p>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.</p> <p>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<img class="emoticon" src="https://pfspipe.ipmu.jp/jira/images/icons/emoticons/help_16.png" height="16" width="16" align="absmiddle" alt="" border="0"/> of built in groups (if no there is no control on issue happened).<br/> 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.</p> <p>Having pfs-jira-admin in the jira-developers group is fine. <br/> But it seems that non of the jira-ldap-* users are being propagated to the jira-developers group.<br/> I can add them all explicitly, but there does seem to be an LDAP issue.</p> <p>Because it is not possible to have one JIRA group as a member of another, I have added, <em>temporarily</em>, all the individual members of the jira-ldap-users group to the jira-developers group.</p> <p>This change should be reverted as soon as a long-term solution is understood and implemented.</p> <p>Priority dropped from blocker to major. I suggest that this issue remains open until the aforementioned long term solution is found,</p> Duplicate INFRA-200 Relates INFRA-200 Development Rank 0|ii04on: