Remove extra step when adding exclusion reasons on the fly#416

When adding an exclusion reason on the fly, instead of hitting add and then having to reclick and scroll to the bottom (screenshots 1&2), I’d like it to show up in the bar as soon as you add it (screenshot 3). Makes the most sense to me and saves a bit of time! :)

Thanks Jade! We debated this at the start… we envisioned that people might want to create reasons but not apply them, but my use is similar to yours (If I configure a reason, I want to apply it 100% of the time).

Does anyone have a typical workflow that involves creating but NOT applyiing exclusion reasons? Let me know, bc my use aligns with what Jade’s described!

Exactly, but in my head, that’s the whole point of the Configure Exclusion Reasons page. Are there times when using this page to create reasons ahead of time before screening isn’t the typical workflow? If so, maybe we should make a clearer distinction between this page being for anticipated exclusion reasons, and creation of reasons during screening being on the fly. Otherwise I imagine the configure exclusion reasons page becoming redundant by lack of use and the page’s other features becoming unknown in the process

1. Totally on board with auto-selection of the new option. I’m frustrated we don’t do that already! I do think the user should still have to click “Exclude”, so that it’s perfectly clear what they’re doing.
2. The exclusion reason configuration page will likely always need to exist, to allow creating a PRISMA diagram to user specification.

Definitely. I think this feature pairs well with maybe a greater emphasis on the user support side to guide users to the Configure Exclusion Reasons page before screening instead of showing them they can create them during screening as well.

Complete with release 1.38.0. Thanks Jade!