Add update/close ability to tickets #5

Closed
opened 2020-08-04 14:27:09 +00:00 by luketainton · 4 comments
luketainton commented 2020-08-04 14:27:09 +00:00 (Migrated from github.com)

Is your feature request related to a problem? Please describe.
Tickets are currently read-only through the UI.

Describe the solution you'd like
A page need to be created to update the ticket, and update/close buttons need to exist on the view page.

Additional context
For traceability reasons, we DO NOT want to add delete functionality.

**Is your feature request related to a problem? Please describe.** Tickets are currently read-only through the UI. **Describe the solution you'd like** A page need to be created to update the ticket, and update/close buttons need to exist on the view page. **Additional context** For traceability reasons, we DO NOT want to add delete functionality.
luketainton commented 2020-08-06 18:46:15 +00:00 (Migrated from github.com)

Put these buttons where the black rectangle is on the screenshot (like on the home page):

Screenshot 2020-08-06 at 19 43 43
Put these buttons where the black rectangle is on the screenshot (like on the home page): <img width="1792" alt="Screenshot 2020-08-06 at 19 43 43" src="https://user-images.githubusercontent.com/22561713/89569986-6ba75100-d81d-11ea-92ff-e063939ab7c7.png">
github-actions[bot] commented 2020-08-06 19:10:35 +00:00 (Migrated from github.com)

Branch feature/issue-5 created!

Branch [feature/issue-5](https://github.com/luketainton/FHeD/tree/feature/issue-5) created!
MrLyallCSIT commented 2020-08-06 19:10:46 +00:00 (Migrated from github.com)

Is your feature request related to a problem? Please describe.
Tickets are currently read-only through the UI.

Describe the solution you'd like
A page need to be created to update the ticket, and update/close buttons need to exist on the view page.

Additional context
For traceability reasons, we DO NOT want to add delete functionality.

Do we want Admin delete functionality?

> **Is your feature request related to a problem? Please describe.** > Tickets are currently read-only through the UI. > > **Describe the solution you'd like** > A page need to be created to update the ticket, and update/close buttons need to exist on the view page. > > **Additional context** > For traceability reasons, we DO NOT want to add delete functionality. Do we want Admin delete functionality?
luketainton commented 2020-08-06 19:40:29 +00:00 (Migrated from github.com)

Is your feature request related to a problem? Please describe.
Tickets are currently read-only through the UI.
Describe the solution you'd like
A page need to be created to update the ticket, and update/close buttons need to exist on the view page.
Additional context
For traceability reasons, we DO NOT want to add delete functionality.

Do we want Admin delete functionality?

Possibly, but that should only be available to admins. In the event that we implement this, we then need to consider implementing a permissions system.

> > **Is your feature request related to a problem? Please describe.** > > Tickets are currently read-only through the UI. > > **Describe the solution you'd like** > > A page need to be created to update the ticket, and update/close buttons need to exist on the view page. > > **Additional context** > > For traceability reasons, we DO NOT want to add delete functionality. > > Do we want Admin delete functionality? Possibly, but that should **only** be available to admins. In the event that we implement this, we then need to consider implementing a permissions system.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: archives/FHeD#5