[SE-4084] Billing v2: UX discovery
Story
"As an invoice system user, I want the UI and processes to be clear so that I can use it inside or outside OpenCraft"
"As an OpenCraft member, I want to know how the UI and features of the new billing software would work in a shared public server, so that we can estimate the cost and value of developing the UI and features"
Full description
After the https://gitlab.com/opencraft/dev/accounting/-/issues/2 discovery has found the requirements (!25 (merged)), find out here how to implement them best and what would it take.
For example we want to answer questions like:
- who would pay for this? What features would they pay for?
- how do we combine solving our own invoicing needs with solving other users' needs? Some requirements we have may be very specific (invoicing periods, CSV format, JIRA accounts, invoice numbering, approval process, …)
- would anonymous users be allowed to register right away? And what would they see?
- would users be ready to give OpenCraft all required invoicing credentials (JIRA, Google, Freshbooks, …) and set them from a web interface?
- would OpenCraft members feel safe having their invoices processed in a public-facing server that handles other companies and that accepts public registrations? Would other companies feel safe sharing server with OpenCraft?
- what are are clients' integration needs? Do they match with ours? E.g. other people might not be using JIRA, or Google login, or Google Drive uploads, or FreshBooks
- are there similar solutions?
- which communities could be reached for consultation or marketing?
In addition, build a mock-up of the software based on the screens/sections/interfaces it needs. See the last part of the #2 (closed) discovery. Identify some of the interfaces (main ones, complex ones, redundant ones, forgotten ones, …), and use this to build an estimate for the UI/UX parts. This will be incorporated into the main estimate.
Completion criteria
- Follow the new process
- Find out answers for questions like the ones mentioned in the description above
- Estimate the cost or complexity of some of the UI-related features, based on the UI and features found in #2 (closed)
- Create MR to adjust the estimates for the UX parts so that we can update the rough estimates in the discovery
- Schedule tasks to do user interviews as needed
- Comment about the list of features/requirements itself based on your opinion
- Participate in the discussion to choose a name
Documentation updates & improvements criteria
- You can add more documentation here through MR. For instance screenshots, mock-ups, ideas, …
Review timeline
- To be decided