Is this even Posible ??

carlosm May 7, 2021

I have a user that needs a form modified to accomplish these actions 

 

User Story [required text]

  • [Example description text]

Activity [required selection]

  • I need to ADD content on company docs.
  • * I need to Edit content on company docs. 

Supporting Artifacts  [required link]

  • Link a confluence page or google doc

Naming [required selection]

  • Current feature/s names/s are: (e.g Save Card Details, Save Beneficiary Details, Mass Payouts, etc.)
  • Has feature/product naming been approved by product marketing? Yes or NO

Brief Description [required text]

  • Brief description of the above product and how it fits into the company Products. What's new, what has been improved or implemented? 

Content [required text]

  • Intro
  • User Workflow
  • API Calls 

Objective [required text]

  • Brief description of what the reader should understand. 
  • Recommended company docs entry points:
  • Help strategize the structure of the document. Where is it located?

Audience [text]

  • All documentation readers e.g. client-side payment managers, PMs, operations managers, developers, etc.

Approvers [user selection]

  • Product Manager - 
  • Product Marketing Manager - Kristin

Target Completion Date [date]

  • XXX

1 answer

0 votes
Michael Blake May 7, 2021
  • In Jira 8.16, admins get the ability to add contexts to system fields like Description - so the its possible on data center 8.16 and the cloud.
  • Activity - just make the field required in the field configuration
  • you may need to get an app to set the "Supporting Artifacts" field to be required on create or another transition.
  • You can name the select fields with the phrase or Question.  You can also have default values for both fields.
  • you would add a single line text field for Brief Description and make it required.
  • the fields under Content would be custom fields.
  • Typically Audience would be either a user picker or group picker field instead of a text field.
  • Approvers would be user pickers based on a role in the project and you can set a default user.
  • Target completion date could use the DueDate field or you can create a date picker field.

As for the layout of the view issue screen, it is governed by Jira (new issue view).  You can change the order of the fields on the Create and Edit screens.

Suggest an answer

Log in or Sign up to answer