Ability to hide summary field

[Freyr Gudmundson]

I managed to create an elegant-ish solution to team-multiassignment as follows:

1. Team type in JPD
2. Atlassian Team field on Team type
3. Initiative type in JPD
4. Team Assignment type in JPD
5. Team Assignment type acts like a many:many table in a relational DB. Has a Team connection field to the JPD team type, and an Initiative connection field to the Initiative type. This allows me to create a Team Assignment item and add information to the connection, e.g. % assigned/capacity used.
6. Using a type this way makes the Summary field get in the way. I could clean it up by simply typing a dash for every summary, but it would be nice to be able to simply hide the summary field in these cases.

As a bonus, if you move the Summary field to any position except the first position, then the field aggregation feature doesn't work for fields the the left of Summary. If the aggregation has already been set, it disappears, but reappears when the field is moved back to the right of Summary.

[Tanguy Crusson · Accepted solution]

Thanks for the feedback. There's no way to disable the Summary field. 

what you could do though is set up an Automation rule that automatically sets a value for the summary when an idea of that type is created.