Assign an issue without having repository #8033
Replies: 7 comments 1 reply
-
|
Complete agree. Is the only reason Im thinking not use github as the main task manager in my company I need to create tasks that are not associated with a repository, but, they are asociated between them like for example in a milestone. As I can see, all tasks in a milestone are dependant of the repository, so you neither can asociate tasks of differents microservices in a way you can handle it together. |
Beta Was this translation helpful? Give feedback.
-
|
Agreed! This would make GitHub issues better than all the heavy handed task managers out there (Jira, Asana, etc.) |
Beta Was this translation helpful? Give feedback.
-
|
Since i just had the same question and google brought me here, i assume this is not the case, still? If it will be possible at all? |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Another issue (pun unintended) is that if I collaborate on a specific repository that my teammate happened to create I cannot create issues for that repository hence cannot connect the project to it. |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 As a consulting firm that uses work tracking tools, we think in this way, so when we have internal initiatives (which may not involve code at all), we tend to gravitate towards managing that work like we manage development work. We can use other tools like Trello or what have you, but we would prefer to use tools the team is already in for this use case. Like with client work, we are creating empty repositories for the initiative, so we have a work around but it would be nice if we could create issues without the unused code repository |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
What im requesting is the ability to assign people to an issue/task without having to select a repository.
At the moment when creating an issue it's simple and often the headline field is enough to define what needs to be done.
And when there are tasks not really releated to a repository it feels weird that you have to add it to a specific repository when there really are no connection between the task and the code repo.
I know that a temporary solution would be to create an empty repo called something like "misc" and use that as a catch all repo for all misc stories.
And I think, until this is resolved, that's the way we will do it.
Alternativly that we would just write it in the issue title "Book meeting with... - Kenny"
But it feels a bit wonky to be forced to have an repo to have misc issues.
So I suggest that you remove that restriction and allow stories to only exist in a board/project without being tied to a repository.
Beta Was this translation helpful? Give feedback.
All reactions