salesforce / oss-request Goto Github PK

Metadata on program defines start tasks. If there is more than one, then the user is prompted to select the task.

If an email is sent to the webhook and it fails, reply with the error.

Potentially do different things depending on the form data.

Enable criteria that can auto-approve a request.

Provide a way (maybe markdown) for putting links in the metadata.

Right now once a task is completed there is no way to go back and change it.

Should an admin or task assignee be able to edit the data on a completed task?

When viewing the /requests list, I would like a search box that filters requests by name so I can more easily find the request I am interested in.

Filtering could be accomplished with a client-side javascript filter that hides non-matching rows.

Will enable migrations or the app to understand the task persisted prototype when the schema changes.

If a URL with query params is sent to a user that needs to login, it seems that once logged in those params (or maybe the whole URL) are lost.

Can we pull in the actual metadata?

Use a better JSON web editor.

Group metadata is always fetched fresh. But references to groups are stored with the request. So those references can become stale.

Add Task - Should it disable tasks which depend on other tasks which aren't there?
Task List - Should the dependency graph be shown somehow?

Emails about comments should have a URL that pulls up the comments.

• Lock the button until a response is received
• Maybe show a spinner

When viewing the /requests list, I would like a way to filter the requests by status so I can quickly find the request I am looking for.

Example: A dropdown for status - Approved, Conditionally Approved, In Progress, Denied

Hi James ,

I tried running this app in local as well as deployed to Heroku but in both the places I was getting below error,

Ask timed out on [Actor[akka://application/user/$a#-1415981005]] after [15000 ms]. Sender[null] sent message of type "services.GitMetadata$GetAllVersions$"

Thanks,
Nishan

If a task assigned to a service is deleted, give it a chance to clean up.

When viewing the list of requests, I would like the list to be alphabetized so I can easily find a specific request in the list.

Just prompt for request name when linking to http://asdf.com/request?program=zxcv

Admins and Task owners should be able to reassign them. A notification should be sent to the new owner(s).

If two or more concurrent fetches for metadata happen, one can fail because if (!baseDir.exists()) { - the dir exists but the git clone hasn't completed.

Right now a user must own an access token for access to the Metadata URL. It'd be better if that was owned by the org.

One option is a GitHub Deploy Key: https://developer.github.com/v3/guides/managing-deploy-keys/#deploy-keys

Another option is a GitHub App: https://developer.github.com/apps/getting-started-with-building-apps/

Pick a Heroku Addon we want to support out-of-the-box in prod. Default to some STDOUT thing in dev.

Add the email logic to the DAO.

If someone comments on a task that is assigned to them, and a request they own, a notification with no recipients is created.

The UI should detect URLs and make them into clickable links.

Possible solution: https://alexcorvi.github.io/anchorme.js/

Currently it is fetched on first use and cached in memory for the duration of the process.

On new request, instead of a drop down, use a selectable list and provide a program description in each item. Description should come from metadata and support markdown.

The UI and the DAO should implement record security. For example:

• Only admins can complete a request
• Only admins or an assigned user should be able to update a task

Provide a way to create a new task post approval on some time-frame. Like every 6 months add a new IP Approval task.