ravendb / samples-yabt

"Yet Another Bug Tracker" solution sample for RavenDB and .NET with Angular UI
https://yabt.ravendb.net
MIT License
107 stars 22 forks source link

[Feature] Functionality to create new backlog item from the frontend #54

Open chesthar opened 1 year ago

chesthar commented 1 year ago

As an end-user exploring the system and checking what's happening in the backend and the DB I would like to have the functionality to create a backlog item(let's say only type bug is enough) from the front-end. Currently performed some basic operations from the swagger and seems to be working(on the local instance) but was hard to guess the payload that I have to pass to /api/BacklogItems/bug. So I think this functionality will make this project and of course the magnificent ravendDB more and more attractive to new users like me.

SUT details: RavenDB 5.4.2 local instance(windows) yabt latest master: 6a6d72cbd15cd5f8c601b51ce470e382e0f363b2 browser Chrome: 105.0.5195.102 OS: Windows 10 Enterprise Visual Studio 2022 Pro

AKlaus commented 1 year ago

Hey @chesthar,

Not sure I understand where's the problem. The swagger API is well-documented (screenshot below) and you can try it not only locally but also on the website itself (yabt.ravendb.net/swagger). The database gets recreated weekly.

Getting one level down from API to the services, you can check out the automated tests for creating of backlog items at BacklogItem_Crud_Tests.

There's also a TicketImporter tool that calls those services for creating new backlog items from a chosen GitHub repo (line of code)

Based on that, there's not much need in the front-end functionality to create backlog items as it's deemed pretty trivial (editing is more complex and provided on the UI).

image
PureKrome commented 7 months ago

@AKlaus I believe the question asked, is: Can we add a bug via the UI and not the (Swagger) API?

EDIT: I came here to ask the exact same question as I hit the UI website first. not the swagger API.

AKlaus commented 7 months ago

Hi @PureKrome, Adding a bug (or any other ticket type) via the UI hasn't been implemented, as the API is already there and the UI part was deemed a trivial task compared to editing. Of course, if someone submits a PR with the implementation, the team wouldn't mind 😊

BTW, all the existing tickets have been created by running the TicketImporter (under tools/TicketImporter) that copied 50,000 tickets from 2 public repos: dotnet/aspnetcore, dotnet/runtime.