[BE + FE] Editing mode

[thogebati]

Description

Remove Requesttype popup, this will now happen in the form below.

After creating the ticket in the draft mode, it should be printed in the chat as an still editable form (#187).

Below the form another message is printed into the chat: " Your ticket has been created successfully! Take a look if the printed information accurately captures your concerns. If you are happy with the details, use the "Send" button to submit it. Otherwise you can edit your ticket directly by clicking on the corresponding fields and confirm your changes by pressing the "Send" button. In case you want to start again or the ticket is no longer required, you can end the process with the "Cancel" button."

The table should include editable fields of their respective kind (text fields (title, description) whereby the user should be able to change text freely, while fields with predefined values (the rest) should show a drop-down menu). The user can confirm his changes and finally submit via the "Send"-Button or cancel the ticket creation via the "Cancel" button. Upon pressing the "Send" button, the ticket is switched draft mode to submitted mode and the following message appears: "Thanks! I have successfully submitted your ticket.". If the user presses the "Cancel"-Button, the following message is printed "All right, we have canceled the creation of your ticket at your request."

After either pressing the "send" or "cancel" button, the content in the form should no longer be editable. [Optional: the input fields the form turns grey after pressing one of the two buttons.]

User story

1. As a user
2. I want / need check if all field are correctly filled
3. So that I get the best possible ticket.

Acceptance criteria

• The messages are displayed as written above
• The buttons are shown correctly and can be pressed + the function is as described
• All form fields are displaying the correct input method
• When pressing safe in edit mode the changes are correctly inputted to the ticket

Definition of done (DoD)

• Work products are uploaded to the Github repository and merged to the main branch
• If necessary, the bill of materials section of the planning documents is updated
• Code/feature passes suited tests
• Code is peer-reviewed
• Help documentation (README) is updated
• Fits into our architecture, where possible

DoD general criteria

• Feature has been fully implemented
• Feature has been merged into the mainline
• All acceptance criteria were met
• Product owner approved features
• All tests are passing
• Developers agreed to release

[AnnaH3003]

Here an idea how the sequence of messages could look like (please ignore the missing ticket information, the form should be filled with the generated ticket):