We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • 195
    • 55
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      The button "Configure fields" on first screen, when creating an issue, is always enable for users. The only possible workaround for this button is to set all fields as required/mandatory fields.
      I would like to have an option to enable or disable this button for users so they will be not able to configure fields by their own.

      In Addition: The workaround of making the fields required doesn't seem to work for all custom field types. For instance it doesn't work for checkboxes in all JIRA versions I tested, and doesn't work for Select List (Multiple Choices) as well in JIRA 6.1.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • 195
              • 55
              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

                The button "Configure fields" on first screen, when creating an issue, is always enable for users. The only possible workaround for this button is to set all fields as required/mandatory fields.
                I would like to have an option to enable or disable this button for users so they will be not able to configure fields by their own.

                In Addition: The workaround of making the fields required doesn't seem to work for all custom field types. For instance it doesn't work for checkboxes in all JIRA versions I tested, and doesn't work for Select List (Multiple Choices) as well in JIRA 6.1.

                        Unassigned Unassigned
                        derrick.fans Derrick
                        Votes:
                        146 Vote for this issue
                        Watchers:
                        103 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            derrick.fans Derrick
                            Votes:
                            146 Vote for this issue
                            Watchers:
                            103 Start watching this issue

                              Created:
                              Updated: