Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancements to the workflows #9

Closed
veggiematts opened this issue Mar 14, 2016 · 4 comments
Closed

Enhancements to the workflows #9

veggiematts opened this issue Mar 14, 2016 · 4 comments
Labels
enhancement This is an enhancement (not a bug)

Comments

@veggiematts
Copy link
Contributor

Restart a completed workflow: Users should be allowed to restart a new workflow by selecting a workflow from a pre-defined workflow list or restart the current completed workflow. The current CORAL functionality does not allow users to restart any already completed workflow.

Ability to archive previous workflows: Previously completed workflows contain valuable information, such as date when tasks are completed, and such information should be kept. Currently CORAL does not support such functionality.

Ability to add a step in the workflow for a particular resource: The ability to add a step offers users greater flexibility to determine a customized workflow for a specific resource. CORAL provides a globalized add a step function in the Admin section, which applies to all resources associated with this workflow, not on individual resource level.

Receive assignment email notification with some context about the assignment: Users have complained that the workflow assignment emails sent from CORAL do not contain much useful information. It would be helpful to embed a concise message in the email about the assignment rather than just “a resource is added to your queue” as is currently displayed.

Send email reminder to users who are assigned to a step: Task reminders are often seen in project management application or task management tools. This functionality will remind users to complete the steps by a due date. CORAL has alert function in place now, but only for subscription alerts.

@veggiematts veggiematts added the enhancement This is an enhancement (not a bug) label Mar 14, 2016
@benheet
Copy link
Contributor

benheet commented Mar 18, 2016

for a point of discussion, what is everyone's preference on the specificity of issues? for example, this issue notes several pieces of altered functionality. should these be pulled out into separate issues for more focused discussion or is containing them together in a single issue better?

@xsong9
Copy link
Contributor

xsong9 commented Apr 1, 2016

NCSU is working with Matt refining the development on individual function described here. Separate issues will be added soon. Meanwhile we are happy to collect any comment or feedback you may have about these functions.

@xsong9
Copy link
Contributor

xsong9 commented Nov 9, 2016

Have SC reviewed this issue yet? There is a pull request #117 for this issue.

jcuenod pushed a commit to jcuenod/Coral that referenced this issue Dec 2, 2016
@jeffnm
Copy link
Member

jeffnm commented Mar 15, 2018

#117 was merged over a year ago, I'm assuming this can be closed.

@jeffnm jeffnm closed this as completed Mar 15, 2018
queryluke pushed a commit to queryluke/coral that referenced this issue Jan 22, 2020
…s-3.0.1-compat

ERM-56: Long load times in the Resources module
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement This is an enhancement (not a bug)
Projects
None yet
Development

No branches or pull requests

4 participants