# Issue As FHIR artifacts mature, WGs will be required to resolve issues in ways that are constrained by the maturity level. For example, someone could request a breaking change to a normative resource. The WG likes the idea, but decides that it cannot make the requested breaking change. Today, the ticket is either: * rejected * not persuasive with mod When tickets are resolved this way, the fact that the decision was based on maturity is lost. It is important to track requests that are rejected for this reason so we: * have some idea of the 'penalty' we are paying for maturity * can determine if/when it makes sense to attempt a group of them anyway (whether going for a large set of breaking changes, retiring a resource, etc.). # Proposal Add a tag to Jira, `resolution-constrained-by-maturity`, which can be used to track this type of disposition. Add guidance to Confluence: > The `resolution-constrained-by-maturity` tag should be used by a WG when the maturity of an artifact has resulted in the resolution disposition. For example, if a WG agrees with the request for a breaking change to a resource but cannot meet the requirements to _perform_ a breaking change. This tag is appropriate whether the ticket ends in a `Rejected` status or in flavor of `Not Persuasive` ( e.g., if the WG agrees to define a standard extension instead). Notify WGs of the additional tag and guidance, with a request that they track this information. # Additional * Further discussion on [Zulip](https://chat.fhir.org/#narrow/stream/179192-fmg/topic/Standard.20Status.20Rejection)