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-91 Software Development Infrastructure <p>Some ticket e.g. <a href="https://pfspipe.ipmu.jp/jira/browse/INFRA-79" title="Configure auto-add new LDAP users to jira-user/developer" class="issue-link" data-issue-key="INFRA-79"><del>INFRA-79</del></a> has Resolution:Unresolved with Status:Done.<br/> Check status workflow or something to set resolution in simultaneous with status...</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=swinbank" class="user-hover" rel="swinbank">swinbank</a> any idea (could you help)?</p> INFRA-91

Check status workflow that some has Status:Done with Resolution:Unresolved

Story Major Done Done swinbank shimono Thu, 1 Dec 2016 07:09:00 +0000 Tue, 6 Dec 2016 11:59:19 +0000 Tue, 6 Dec 2016 11:59:19 +0000 0 2 <p>I'll take a look shortly.</p> <p>Normally, when an issue is moved to the "done" (or "won't fix", etc) state, a "post function" on the transition should set the resolution appropriately.</p> <p>That's certainly the case in the "Agile simplified workflow for DM with reopen" which is being used by these tickets.</p> <p>However, that workflow was only just applied, moving away from the default "jira" workflow. It's possible the "jira" workflow wasn't setting resolution appropriately, or that it somehow got garbled in the change of workflows.</p> <p>I've re-applied the "done" status to all the affected issues (there were five of them: <a href="https://pfspipe.ipmu.jp/jira/browse/INFRA-71" title="JIRA relogin forces to move top page" class="issue-link" data-issue-key="INFRA-71"><del>INFRA-71</del></a>, <a href="https://pfspipe.ipmu.jp/jira/browse/INFRA-75" title="Define naming convention for JIRA project/key" class="issue-link" data-issue-key="INFRA-75"><del>INFRA-75</del></a>, <a href="https://pfspipe.ipmu.jp/jira/browse/INFRA-76" title="Wire in outgoing mail" class="issue-link" data-issue-key="INFRA-76"><del>INFRA-76</del></a>. <a href="https://pfspipe.ipmu.jp/jira/browse/INFRA-78" title="Configure JIRA instance w/ installing plugins" class="issue-link" data-issue-key="INFRA-78"><del>INFRA-78</del></a> &amp; <a href="https://pfspipe.ipmu.jp/jira/browse/INFRA-79" title="Configure auto-add new LDAP users to jira-user/developer" class="issue-link" data-issue-key="INFRA-79"><del>INFRA-79</del></a>), and the resolutions have now all been set appropriately.</p> <p>I don't think this should recur, unless there's some need to change the workflow again in the future.</p> <p>Thank you for helps!<br/> Looking at workflow management page <span class="error">&#91;1&#93;</span>, newly created projects has its own copy of default workflow, which is quite different from our standard (for now) "Agile simplified workflow for DM with reopen". I've switched FIBERALOC and SURVEY to the default.<br/> I suppose these tickets from non-DRP projects had such default workflow, and this kind of strange behavior happened.</p> <p>*1 <a href="https://pfspipe.ipmu.jp/jira/secure/admin/ViewWorkflowSchemes.jspa" class="external-link" rel="nofollow">https://pfspipe.ipmu.jp/jira/secure/admin/ViewWorkflowSchemes.jspa</a></p> <p>Added comment to <a href="https://pfspipe.ipmu.jp/jira/browse/INFRA-90" title="Add procedure document on service management" class="issue-link" data-issue-key="INFRA-90"><del>INFRA-90</del></a> to add into procedure manual.</p> Development Rank 0|ii014v: Reviewers atsushi.shimono