Hi Keong, Thank you for feedback. I believe the way it works is that Resolution is Unresolved by default upon creation of an issue and stays in that state until Jira is "Delivered" (aka Resolved in the Atlassian default workflow naming convention) or "Closed. The Resolution field should be visible when we transition to those two states; however, that is not how LF has set it up on some of the projects.
We can correct this by asking LF to only make Resolution a visible/editable field only in cases where we are transitioning to Delivered or Closed. I think Jira always intended to allow users to update Resolution field since it provides multiple default Resolution tags. If a user does not manually update the Resolution, then everything is just marked Done, which does not provide enough insight to what true disposition of a ticket. Also, on Reopen, the Resolution should be reset to "Unresolved" Maybe LF can comment more on this. Thanks, Randa -----Original Message----- From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of Keong Lim Sent: Wednesday, August 08, 2018 9:52 PM To: onap-discuss@lists.onap.org Subject: Re: [onap-discuss] Jira workflow change for designated projects Hi Randa, Just wanted to point out that when a user manually sets the "Resolution" field in JIRA, the server also automatically sets the "Resolved Date" field, even if the "Resolution" is "Unresolved". This is already causing confusion in JIRA and its widgets because some of them use "Resolved Date" as an indication of the case being "resolved", whereas others filtering on the text of the "Resolution" field. Taking a specific example, https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_SDNC-2D357&d=DwIFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=kyPZ229JImvwwKH-78nlyg&m=y4YMrDywk9gMLi63Yk9d89OwlPwEosfDBV034KrPWlw&s=Vsb2z49uLt6_I9NnsxT_kHkAaAP58l_zAmJ-WV99MAM&e= is currently "Unresolved" with "Resolved Date" of "28/Jun/18". When viewed on the Agile board, it is displayed with a "strikethrough" style, indicating it's "resolved" and when using burn-down charts widgets, etc, it will be counted towards "resolved" cases, throwing off all the stats. Instead of direct changes to the "Resolution" field, it should be part of the workflow buttons, so that the "post transition functions" can do things like: - set the "Resolution" field - clear the "Resolved Date" to more appropriate values, reducing confusion. Keong On Thu, Aug 9, 2018 at 05:44 AM, Randa Maher wrote: > > I want to ensure that projects that are using workflow v.3 have > access to Resolution field in their Edit screen since this field work > in tandem with the Status field for this workflow. > > The options that are currently available for Resolution are as follows > > * Unresolved (default) -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11787): https://lists.onap.org/g/onap-discuss/message/11787 Mute This Topic: https://lists.onap.org/mt/24212780/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
