Email threading settings regression bug and fix advice
What happened?
We recently discovered that a regression had occurred that unfortunately altered the settings related to issue association via email threading:
Profile > Project Mapping > Pre-processing > Issue Association > Use References Header
Profile > Project Mapping > Pre-processing > Issue Association > Use In-Reply-To Header
Due to the way this regression had occurred, we did not detect the regression as soon as we should have, and the window to rollback the configuration had closed.
How am I affected?
The regression caused the above settings to be effectively inverted in profile project mappings:
If a project mapping inherited one of the above settings from the default mapping (or a parent mapping in the case of rules), it was set to be disabled instead.
If a project mapping had one of the above settings disabled, it was set to be enabled instead.
What should I do?
Check the above settings in your profile’s default project mapping. Ensure it is set as you want it to be.
If you want all other project mappings/rules to use the same configuration for these settings, tick the new checkboxes before saving:
If you require some projects to have different configuration for these settings, consider using the new checkboxes from step 2 in order to reduce the amount of changes you need to make by inheriting the most common set up and then adjusting individual mappings as required.
A note from us
Before this problem was detected, we had already undertaken development process changes internally with the aim of preventing such occurrences (ironically, this regression had already occurred by this time). We are confident that going forwards we will attain the levels of reliability and robustness that our customers both expect and deserve.