chasinglogic / praelatus-go Goto Github PK

For example I should be able to call /api/projects?permission=CREATE_TICKET to see all projects I have CREATE_TICKET permission to.

Show ticket component for a single ticket. Including relevant functionality

spf13/cobra is becoming a standard among Go CLI tools. Additionally urfave/cli is getting ready to undergo a major breaking change from v1 to v2 and cobra is generally faster than urfave and more customizable.

Something is wrong with the css that makes the text black occasionally. Need to find the appropriate selector and fix it.

This includes the following features:

• Creation and Management of Custom Fields
• Creation and Management of Workflows
• Creation of Projects
• Creation and Management of Field Schemes
• Creation and Management of Permission Schemes

So far the Indexes I know we need to create are:

Tickets

• Key
• Text Index: Summary
• Reviewer
• Assignee
• Status
• Ticket Type
• Created Date
• Updated Date

Projects

• Key
• Project Lead

Everything Else

• Name

Currently the editor does not handle nested lists well. Additionally when a user is in a list and presses tab we should nest the current entry for them.

Using VueDraggable or some similar library

there is a bunch of old test code that needs updated or rewritten

We need to import the old app layout to Vue.js this means getting the navbar down, getting the sidebar in place, and making it easy to extend them.

i.e. key in ("TEST-1", "TEST-2")

This includes:

• Creation and Management of Ticket Types
• Management of Users in project and their roles
• Creation and Management of Roles
• Changing Field Scheme
• Changing Workflow Scheme
• Edit Projects Data (Description, repo, upload new icon, etc.)

Currently you can basically send any value in for a custom field and we accept it. We should check that we aren't getting strings for int fields, etc.

We need to verify the godoc looks correct and has correct information.

A lot of our tests only check that the program gives me what I want when I give it what it expects. We should check for error cases and obvious miss inputs (such as anonymous access causing actioning user to be nil)

ModifierStatement will potentially have to be modified to support this or we can decide that it should all be pushed into the Repo to handle this.

It's broke. Fix it.

Document how to actually use this thing

Currently the mongo repo does not support ticket updates, pending the ability to handle field scheme validation.

When a user is created a list we automatically add a - to the beginning of the line. When a user presses this twice without entry we should stop adding to the list and clean up the erroneous entries. For example:

- item 1
- item 2
- 

If the user presses enter here they will get

- item 1
- item 2
- 
- 

The expected behavior that if they press enter again from this position they will end up with this:

- item 1
- item 2

| <- cursor here

This should work for numbered lists as well

• Write the component
• Hook it into the router

As it is we call /api/users/{username}/avatar to get the url then bind that to the src attribute of the img tag. We should instead just be able to use that api endpoint as the src attribute directly and let the API stream the appropriate image.