Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-77876

Support for required fields for Jira issue creation in MS Teams

XMLWordPrintable

    • 2
    • 13

    • 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.

      Currently, only a standard set of fields like "Project", "Issue Type", "Summary", "Description", "Priority", "Assignee" are supported and available in the JIRA issue creation form.

      Hence, if there are any REQUIRED fields in the Jira issue create screen, the issue creation will fail and the following error will appear: “(field name) is required”

      Please support the REQUIRED fields in the MS Teams for Jira issue creation.

       

      Group Picker ( multiple groups ) which is Advance custom field is not visible on create issue screen of Jira cloud add-on for MS Teams , though the field is Optional. Other standard custom fields ( though mandatory ) are visible while creating issue

        1. image-2023-03-22-15-28-28-755.png
          image-2023-03-22-15-28-28-755.png
          26 kB

            [JRACLOUD-77876] Support for required fields for Jira issue creation in MS Teams

            Efrat Barak Zadok added a comment -

            I am facing the same using Slack

            Efrat Barak Zadok added a comment - I am facing the same using Slack

            Harry Weppner added a comment -

            Can this issue please be re-classified as a bug and treated accordingly?

            Harry Weppner added a comment - Can this issue please be re-classified as a bug and treated accordingly?

            Simon Duerr added a comment -

            Same thing over here, the fact, that the teams integration uses some default set of fields (instead of those specified in the issue creation screen) makes the integration useless for any project requiring other fields (like component, epic....).

            Thank you for a solution of this issue!

            Simon

             

            Simon Duerr added a comment - Same thing over here, the fact, that the teams integration uses some default set of fields (instead of those specified in the issue creation screen) makes the integration useless for any project requiring other fields (like component, epic....). Thank you for a solution of this issue! Simon  

            Manja Vogel-Kautz added a comment -

            Hi guys, without the possibilty to fill mandatory fields when creating an issue from MS Teams, the App is useless for several of our projects. So the option would be very much appreciated

             

            THX and kr

            Manja

            Manja Vogel-Kautz added a comment - Hi guys, without the possibilty to fill mandatory fields when creating an issue from MS Teams, the App is useless for several of our projects. So the option would be very much appreciated   THX and kr Manja

            Erik Vanderstraeten added a comment -

            Required fields upon creation is a good way to keep your data clean as from the start.

            So, we really would like to be able to use the same creation screen in Teams as configured in Jira for the chosen Issue Types

            Erik Vanderstraeten added a comment - Required fields upon creation is a good way to keep your data clean as from the start. So, we really would like to be able to use the same creation screen in Teams as configured in Jira for the chosen Issue Types

              Unassigned Unassigned
              ssreedhar@atlassian.com Shashank Sreedhar
              Votes:
              24 Vote for this issue
              Watchers:
              24 Start watching this issue

                Created:
                Updated: