As a schema admin I want to be able to make one or many reasons for issue required fields before a user can send an issue or a particular type.
Requiredness should be configurable per issue type/field set combination. E.g. a "For Checking" field set may be required on Issue Type A but not required on Issue Type B.
Allow each reason for issue (field set) to be marked as required or optional for each issue type.
When viewing an issue type, indicate whether a reason for issue (field set) is required.
When sending an Issue, indicate which reasons for issue are required.
Do not let the issue be sent until the required reasons each have recipients specified.
|
Practical use of functionality?
Ensure that users sharing a document send it to people for check, review, and approval. |
|
|
What is the impact of not doing this?
Users could share documents and neglect to send for approval by mistake. |