Detail Future Goals/Plans
License and Copyright Notice
By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).
What is the goal or the problem, and why is it important?
The purpose of this issue ticket is to create documentation for the future goals/plans of ViewOrder. Although the main functionality of this component is simply to enable administrators to view orders directly on the page, there were additionally some "stretch" goals that may not be reached within this semester's time-frame. These goals include "paging" (e.g. allowing administrators to view up to ten order details in a page), automating tests both on an individual component level (i.e. automating tests for frontend, backend, APIs, etc.) and larger integration level (e.g. testing functionality between ViewOrder and PlaceOrder consistently), and authenticating users. It is significant to document these potential features for future developers to gain an idea for the next direction of ViewOrder, either to add on to its functionality or to improve it.
Context: Pagination can be seen as the process of splitting a document into discrete pages
How are you going to achieve the goal or solve the problem?
A document will be created (or edited in the case of the ReadMe.md route) within ViewOrder's Planning to outline the future goals of ViewOrder. Additional discussion with the Product Owner may be required to refine details.
What will be produced as a result of this effort and where will it live on GitLab?
A document detailing what goals/steps next-in-line for ViewOrder will be produced and live within ViewOrder's Planning repository.
Give a justification of weight or due date.
This issue is given a weight of 4, which is equivalent to a 1-person week due to requiring some discussion to refine what features/functionalities will be desired in the future and then creating and formatting the document for coherency and readability. There may be some communication lag that may extend issue ticket time for more than two days.
Who will do it, and what will they do?
Any individual may take on this issue ticket and create a document to detail future goals/plans for the next team of developers (that may work on ViewOrder).
What was the outcome?
This will be updated at a later date.