Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11203

Custom Field cannot be added to a Card unless it's applicable for all ticket types

      In 6.6.0 the option to customise cards in the new Agile boards was added, however the field I need to add is unavailable, it appears only fields which are available on all ticket types are available - this is a regression from the Classic boards, where I could add this field.

      Repro steps:

      1. Add a custom field.
      2. Ensure it's setup to work with a project that uses a JIRA agile board.
      3. Customise the Agile board and try to add the newly created custom field.
        > It works!
      4. Modify the custom field to only be applicable to one ticket type, Story for instance.
      5. Now try and add the custom field to the ticket.
        > The field is no longer available.

      The use case is that sub-tasks have a different set of fields to regular issue types.

      Ideally if a field is not available for an issue type then it just wouldn't appear, but if it just had 'EMPTY' that would be fine also.

      I've put priority as major as this will block us moving from the classic boards.

            [JSWSERVER-11203] Custom Field cannot be added to a Card unless it's applicable for all ticket types

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.06
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2851360 ] New: JAC Bug Workflow v3 [ 2934342 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2544039 ] New: JAC Bug Workflow v2 [ 2851360 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549374 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2544039 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: fixme warranty New: affects-server fixme warranty
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 909270 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549374 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 747520 ] New: JIRA Bug Workflow w Kanban v6 [ 909270 ]
            mtokar.adm made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 728649 ] New: GreenHopper Kanban Workflow 20141014 [ 747520 ]
            David Tang (Inactive) made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Hi Oliver,

            Thanks for your feedback on JIRA Agile.

            The behaviour you have requested is in fact the expected behaviour - a custom field should be available to be added as long as the field applies to any of the issue types (and projects) that match the board's filter. We have attempted to reproduce the bug using the steps provided but have been unsuccessful. We believe the bug is more specific to your case.

            To help us diagnose the problem, could you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and with higher security.

            Regards,
            JIRA Agile Team

            David Tang (Inactive) added a comment - Hi Oliver, Thanks for your feedback on JIRA Agile. The behaviour you have requested is in fact the expected behaviour - a custom field should be available to be added as long as the field applies to any of the issue types (and projects) that match the board's filter. We have attempted to reproduce the bug using the steps provided but have been unsuccessful. We believe the bug is more specific to your case. To help us diagnose the problem, could you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and with higher security. Regards, JIRA Agile Team

              Unassigned Unassigned
              6c8e2aa384e8 Oliver
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: