Can custom fields be grouped/organised?

[Keith Furnell]

Three custom fields are offered in the free plan as a teaser for the standard and premium paid plans (offering 50 and 100 respectively).

For those that have signed up, are those custom fields just presented as a big alphabetic list, or is there any functionality to group related fields?

Would imagine that with 20+ fields that some level of organisation becomes required, and hopefully that isn't just crudely through judicious selection of field names?

[Enrique Serrano Valle]

Hello again, @Keith Furnell !

You raise a good point regarding field organization, and it's something that we're tracking in our backlog of suggestions. At the present time I can't provide a specific roadmap for when such a change would be implemented, but we appreciate your feedback.

In practice, our internal and external users are currently doing something similar to what you suggested, prefixing related custom field names with the same root, so that related groups would stay together.

[Keith Furnell]

Thanks @Enrique Serrano Valle. I guess you're referring to a suggestions backlog other than the public https://jira.atlassian.com/issues/?jql=project%3DCOMPASS%20AND%20type%3DSuggestion%20AND%20statusCategory!%3DDone.

When tackled, it would be good if:

1. there could be two levels of grouping - for example to support a group of "Version" fields, and within that group pairs of single-select and number fields (e.g. "Test Framework Type" and "Test Framework Version")
2. fields and groups could be explicitly ordered, rather than just alphabetical