Skip to content
Documentation Portal →

Who sets what

An issue carries a handful of labels and fields. The split is simple: facts are yours, judgements are ours — and the Portal never presents your proposal as our decision, or the other way round.

On the issue Who sets it Meaning
Title & description You (editable by you afterwards) The report itself
Type — Bug / Feature / Task You propose on the form; the team confirms What kind of work this is
Priority You propose; the team sets the final priority Your proposal tells us how it lands on your side
BC version You The version you saw the problem on
Target date You (Features only) When you'd need it — a wish, not a booking
Status — Open / Closed You (your own issues) and the team Whether work remains
Planned for The team The release your fix or feature is scheduled into

The lifecycle, in practice

  1. You report — the issue opens, your organisation can read it, the team is notified.
  2. We respond — questions and findings arrive in the thread; you get an e-mail per reply.
  3. It gets scheduledPlanned for shows the release once the work is slotted.
  4. It ships — the release appears under Releases, with notes.
  5. It closes — by you when you're satisfied, or by the team with a closing reply. Reopen it if the problem returns; that beats filing a duplicate.

When we e-mail you

You hear about the issues you reported. Four moments, and no others:

We send When
We need something from you We cannot go further without an answer, a screenshot or a version number. Work is paused until you reply
Looks resolved We believe it is fixed — confirm, or reopen it if the problem is still there
A reply Somebody on the team answered in the thread
Closed or reopened The issue changed hands between open and finished

Nothing is sent for In progress or In review. Those are visible on the issue whenever you look, and an e-mail for each would bury the two that need you.

Turning it off. Settings → Notifications → "Email me about my own issues" stops the reply, resolved, closed and reopened messages.

"We need something from you" is always sent, even with that switch off. It is the one message that exists to unblock your own report: without it an issue can sit for weeks while we wait for you and you wait for us. The e-mail itself says so, so it is never a surprise.

Your colleagues are not e-mailed about your issues — they can read and follow them in the portal. Organisation-wide e-mail about projects is a separate switch on the same page, off unless you turn it on.