{"version":"2.1.227","anchor":"comment-threads-report-why-they-were-not-resolved","canonical_anchor":"comment-threads-report-why-they-were-not-resolved","heading":"Comment threads report why they were not resolved","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/comment-threads-report-why-they-were-not-resolved","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Comment threads report why they were not resolved\n\nFailing to resolve an artifact thread now says whether you lacked permission or the thread was inactive.\n\n**What**\n\nWhen resolving a discussion thread on an artifact, the result now distinguishes success from two refusals: the person asking is neither the thread starter nor a writer, or the thread was never activated. It appears only where artifact comments are available, which is not on by default in this build.\n\n**Evidence**\n\n`not resolved (not the thread starter or a writer)`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}