[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

I am unsure about the second part of the message here: the tester response phase should be the last phase in PE that students are involved in, so I don't think it is possible for testers to respond during the next phase?

It seems to me that the second sentence of the message here is either outdated (inherited from the dev-response phase) or should be removed.

Good point. These issues are created by a script after the dev response phase has ended but before the tester response phase officially begun (there is a gap in between). Hence, 'next' refers to the tester response phase.

Then in this case, will it be better to keep only the first part of the warning? ie after editing/submitting, instead of having the first line completely disappear (which is its current behaviour), it will be replaced with its first part.

Before editing/submitting:

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

# Team's Response
Duplicate marking test

* List
  * List Item 1
  * List Item 2

# Items for the Tester to Verify

## :question: Issue severity

Team chose [`severity.Low`]
Originally [`severity.VeryLow`]

- [ ] I disagree

**Reason for disagreement:** [replace this with your reason]

-------------------

after editing/submitting:

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI.]

# Team's Response
Duplicate marking test

* List
  * List Item 1
  * List Item 2

# Items for the Tester to Verify

## :question: Issue severity

Team chose [`severity.Low`]
Originally [`severity.VeryLow`]

- [ ] I disagree

**Reason for disagreement:** [replace this with your reason]

-------------------

We need to keep this string exactly as it is, because the same string is referenced by the issue processing script that runs between phases. If the string needs rephrasing, it needs to be done on both CATcher and script side at the same time -- but that can be a separate issue as the bug reported here is about the disappearance of the string only.

Noted! Then I shall stick to the original problem of not removing the warning. Thanks for the clarification!