To introduce Configure Fields (Custom field preference) in Create Issue Screen via URL

XMLWordPrintable

    • 1

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Problem Definition

      • The 'Configure Fields' button which exist in the 'Create Issue Pop Up Screen' is not available in the 'Create Issue Screen that is access by URL'. This seems to be a missing functionality at the moment, and are not configurable at the moment.
      • Inconsistency of configuration as if through Create Issue Screen Popup, user have configured custom-fields-visibility, when access the create issue screen from a URL link will remove this custom-fields-visibility setup
      • To access the URL : https://<your jira URL>/secure/CreateIssueDetails!init.jspa?pid=1234&issuetype=6 , change PID with appropriate project ID and issue type.


      This is needed in order to retain the user preference for the fields on the Create Issue Screen. When we try to create issue using link, Jira looses the custom field preference by the user on the create issue screen and displays all the fields on the screen. Which is annoying for the users who do not want to see all the fileds or all the fields are not useful for users and they have hidden those fileds from screen. It is not necessary to have "Configure Field" button on the screen while creating an issue from link, but Jira must retain the field preference and should only show the fileds which are selected by user through Configure Fields option.

      Suggested Solution

      • To introduce this button in the 'Create Issue Screen that is access by URL' so that consistency can be achieved here.
      • To ensure the user preference for the fields on the Create Issue Screen via Screen Popup coexist on the Create Issue Screen via URL

            Assignee:
            Unassigned
            Reporter:
            Azfar Masut (Inactive)
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: