gitness
gitness copied to clipboard
harness
Issues
Hey @fakerybakery, thanks for your feedback! We don't have built-in issue tracking support as of now, but it's on the roadmap 🚀
Any updates on the schedule for that, guys? And there's any help is needed in some form for this get launched?
@allysontsoares thanks!
We haven't started woking on this yet mainly because we haven't finalized the scope or design. And for this, we would absolutely love community feedback. As an example, one challenge with the GitHub approach to issue tracking is that it is limited to a single repository. What happens when an issue spans multiple repositories?
GitLab solves this with epics. You can have epics at the organization level, and an epic can link to one or many issues at the repository level. When they designed epics, it sort of feels like they were constrained by their existing Issue tracker design. So before we implement something similar, I want to understand if there are better options when starting from scratch.
Azure Devops solves this by implementing issues at the Project level instead of the repository level. These issues can be optionally linked to one or more repositories and branches. This feels like it might be preferable to the GitLab approach, setting aside that I am not in love with the UX (which I think we could improve upon). See below screenshot as an example of how this works in Azure.
We definitely want something more robust that GitHub. If anyone has ideas or preferences, please let us know in this thread.
@allysontsoares thanks!
We haven't started woking on this yet mainly because we haven't finalized the scope or design. And for this, we would absolutely love community feedback. As an example, one challenge with the GitHub approach to issue tracking is that it is limited to a single repository. What happens when an issue spans multiple repositories?
GitLab solves this with epics. You can have epics at the organization level, and an epic can link to one or many issues at the repository level. When they designed epics, it sort of feels like they were constrained by their existing Issue tracker design. So before we implement something similar, I want to understand if there are better options when starting from scratch.
Azure Devops solves this by implementing issues at the Project level instead of the repository level. These issues can be optionally linked to one or more repositories and branches. This feels like it might be preferable to the GitLab approach, setting aside that I am not in love with the UX (which I think we could improve upon). See below screenshot as an example of how this works in Azure.
We definitely want something more robust that GitHub. If anyone has ideas or preferences, please let us know in this thread.
I loved the idea from Azure with issues in project level that can be linked with one or more repos, i didn't use Azure DevOps yet, the UI seems a little messy. But the idea seems really cool and definitely more robust than githubs approach.
Greating
I'am new to gitness. I found that the image size of gitness is much smaller than gitlab. And I quickly learned to use the pipeline function, which only took 5 minutes. It was a great unboxing experience.
I'm searching the roadmap for gitness and want to confirm if it will remain this experience in the long term. Can other functions, such as issue and roadmap, be implemented using plug-ins?
I think they are not doing that (issues/roadmap) anytime soon, the focus probably is the final 3.0 release first.
Hi, is there any update on this? Was thinking of setting up a Git server and trying to decide between Gitea/GitLab/Gitness. cc @johannesHarness
Hi, All.
First, we do plan to build an issue tracker in Gitness and Harness Code in 2024. I will update our Idea tracker and our public roadmap when we have kicked off this work.
For the time being you can vote on the issue here: https://ideas.harness.io/gitness/p/issue-tracker
Thanks, Patrick
