- 🇬🇧United Kingdom longwave UK
I updated the link in #11. I think this will get slightly more use than "Data model changes" which I can't remember the last time I saw filled in.
I also find it somewhat funny that we are known as a CMS for structured content and yet here we are, writing structured content into a free text body field, when we raise issues against our own software - if we used proper fields we could have help text, show different fields for bugs vs tasks, etc.
- 🇬🇧United Kingdom alexpott 🇪🇺🌍
Do we need to update https://www.drupal.org/docs/develop/issues/fields-and-other-parts-of-an-... → to?
One thing that makes me hesitate on this change though is that we need a plan for how this information is going to be used. If it's just just going to sit in the issue summary then not many people are going to see it and the value in writing it is minimal. I realise the issue summary says that this will help the initiative and that's a good thing, but I think the process needs to be a bit more apparent. For example, as this is a new section I think the issue summary template could link to initiative and be more explicit about what is expected - other people are not going to know what to do and whether it is relevant. On a large number of issues, i.e. nearly all bug fixes, this section should be removed or N/a'd.
- 🇬🇧United Kingdom longwave UK
Added to the default issue template and updated the documentation as per the examples in the IS. I also added an ID to the new h3 in the documentation so it can be linked if required.
