Agile Triage Boards - For Enhancements?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2020 02:21 PM
Hello all,
I had a question about the Agile Triage Board, specifically with regard to Enhancements, and whether they should be triaged, i.e. whether a Triage Board should be created with which to add Enhancements to the Backlog, or whether users should simply use the "Create Story" UI Action on the Enhancement record itself, to create Stories which will then appear in the backlog.
It seems to me that the Triage Board makes use of the field "Agile Story" on the triaged record, and the field "Original Task" on the Story record, which is useful when triaging records which have nothing to do with Agile Development. However, when Stories are created as children of Enhancements, in the traditional fashion, using the OOTB "Create Story" UI Action on the Enhancement record, it is the Enhancement field on the Story form which is populated with the Enhancement reference, and not the Original Task field. Therefore it seems to me the Triage Board functionality does not correctly leverage Agile functionality in tying the generated Story record to the Enhancement.
Additionally, if an Enhancement is added to the Backlog via Triage Board, the record appears in the Backlog as an Enhancement. However, if additional Stories are added as children of this Enhancement, then those Stories appear in the Backlog as Stories. Stories and Enhancements look totally different in the backlog.. they are completely different colors. So it makes for confusing UI when some Stories are appearing differently in the Backlog based on whether they were created as a result of an Enhancement being triaged vs by use of the Create Story UI Action on the Enhancement form.
So my question is, do these concerns seem valid to anyone else? Should Enhancements be triaged? Are there other possible complications or advantages to the Triage Board that I am missing?
Thanks
Duncan
- Labels:
-
Agile Development
-
Multiple Versions
- 2,532 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2020 01:33 PM
EXACT question we have as well!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2020 08:30 AM
We experience similar challenges. Maybe we are doing it wrong? I dont know.
Any record that is brought in via the triage board whether it be a defect, incident, enhancement, etc has a story created for it. That is great and I appreciate the functionality, but the data not flowing between the two records has caused a bit of extra work for us.
I've messaged one of the product owners a couple of times with no response.
Hopefully it will be fixed soon.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2020 01:38 AM
We are currently starting with SAFe, but the Triage Board there is very similar to the one in Agile Development.
We also had that question on what should be directly a User Story and what should come in via the Triage Board.
Our answer is that basically everything that is related to the Product development should be directly a User Story. That means Enhancements are most likely not needed to be added via the Triage board. We still use the Triage Board for Enhancements during the go-live period to be able to include the old Enhancements without having to re-create them.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2021 06:14 AM
Hi @Duncan Pedersen - curious if you ever came to any resolution on this. We are just starting to look at using Enhancements/Defects, and this is one of the items I just noticed as our Agile teams are using the Triage Board to manage their story creation.