Being able to configure Hypha’s behaviour when sufficient application reviews have been made. Right now, the application will not auto-advance to the next stage, even though it is technically possible for that to happen.
[Autoadvancing would save fund managers time to manually advance these submissions]
A few thoughts:
- who are these configurations relevant to?
- where in the documentation should each of these pieces of documentation exist?
- what to do about configurations currently not customisable?
The applications process relevant configurations should be findable by fund organisation staff who are involved in choosing which workflow to implement as these configurations will be most useful to them, less so to the technical implementers.
I’ve opened an epic to track the different customisations people may want to request.
I’ve added this on the next week’s maintainers call and next months adopters call agenda.