[INFRA-127] Check whether "Resolution" field can be set not to be required Created: 02/May/17  Updated: 02/May/18  Resolved: 02/May/18

Status: Done
Project: Software Development Infrastructure
Component/s: support
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: shimono Assignee: shimono
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Currently, resolution field is set as required field even if ticket status is open.
Check:

  • resolution field can be set not to be required
  • resolution field can be set as child of status field by value

 Comments   
Comment by cloomis [ 02/May/18 ]

If the Resolution field is removed from the Create Issue screen, what breaks? That should leave Resolution unset, which is what we want, right?

Comment by shimono [ 02/May/18 ]

issue is where to configure...

Comment by rhl [ 02/May/18 ]

I understand that hassan is a Jira master. shimono: would you like me to ask him to help you with this?

Comment by price [ 02/May/18 ]

I rediscovered that I'm an admin, so I've promoted hassan to admin so he can sniff around and make suggestions.
We have a question in to Frossie, LSST's Jira queen.

Comment by price [ 02/May/18 ]

Ah! I removed the "Resolution" field from the "Default Screen" (Admin --> Issues --> Screens --> "Default Screen" --> Configure; remove "Resolution"). The result seems to be active already: "Resolution" doesn't show up under "Create Issue" any more. Let me know if this anything else needs tweaking.

Comment by hassan [ 02/May/18 ]

I think this now works for me. shimono: can you confirm the fix? (after the Golden Weekend of course)

Comment by cloomis [ 02/May/18 ]

Apologies, Paul: I should have just done it rather than toss it in for someone else to do.

Comment by shimono [ 02/May/18 ]

hassan thank you, it's working! i could not thought about that way to fix things.
also, thank someone who marked hassan as jira-administrator (mentioned here as a note that it already finished).

Comment by hassan [ 02/May/18 ]

Thanks shimono, although it was actually @price who solved the problem!

Generated at Sat Feb 10 16:49:41 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.