fork-dev / TrackerWin

Bug and issue tracker for Fork for Windows
461 stars 10 forks source link

[Feature Request] System wide bugtracker reference #337

Open rubenverhoef opened 5 years ago

rubenverhoef commented 5 years ago

First of all thank you for the great software!

I have one question, is it possible to add a system wide setting for the bugtracker? So I do not have to configure it for all repositories and so we don’t have to include the “.issuetracker” file into our repositories.

Gama11 commented 5 years ago

Seems somewhat related to #329.

DanPristupov commented 5 years ago

Do your repositories use the same bugtracker?

rubenverhoef commented 5 years ago

I'm using GitLab as repository server and EasyRedmine as issue tracker. But all repositories use the same bugtracker (EasyRedmine).

DanPristupov commented 5 years ago

Global rules are not supported yet. We might introduce them one day, but right now there's no big reason for that.

So, I suppose the fastest solution for you will be to copy the 'issuetracker' file to .git directories manually.

rubenverhoef commented 5 years ago

Okay, than i will include it in my repositories so all colleagues can use them. But it is not a nice thing to have it included in the repository. Is it maybe possible to search also in the global .git folder for the issuetracker file? So i can put it into the "Global" .git folder and it will work for every repository?

DanPristupov commented 5 years ago

But it is not a nice thing to have it included in the repository.

Why? This is a definition of the convention of mentioning issue tracker in that particular repository.

Is it maybe possible to search also in the global .git folder for the issuetracker file?

I'm not aware of a global .git folder.

I still think that there is an easy and straightforward way to share the issue tracker settings with other users (i.e. to create the .issuetracker file). It will also allow to modify those settings easily in a case the address of issue tracker changed.

rubenverhoef commented 5 years ago

Why? This is a definition of the convention of mentioning issue tracker in that particular repository.

Well, not everyone is using the same gui. And only the Fork guys need this file. For all others this file is garbage.

I'm not aware of a global .git folder.

I have an .git folder in my home directory where i have all my git hooks etc.

I still think that there is an easy and straightforward way to share the issue tracker settings with other users (i.e. to create the .issuetracker file). It will also allow to modify those settings easily in a case the address of issue tracker changed.

That is true, but we have a lot of repositories and when the issue tracker changes we have to edit it in all repositories. Our git hooks which are in the global .git folder are also updated automatically to all users so when the .issuetracker can be placed there we simply can update it also.

Or just put the option dedicated in the Fork application, that is also no problem.

miva2 commented 5 years ago

I would also like global issue tracking. Whether it is in a file in .git or in the Fork application itself. I just used this feature for the first time and thought it's pretty neat! But it is very strange to see a .issuetracker file in my repository. Especially since I am the only Fork user on the team. I currently keep it in my unversioned files.

ghost commented 4 years ago

Re-posting here as requested:

Hi, first let me say thank you for your great tool! While using it for a couple of month in private projects, I decided to use it for my work projects too. In Qt we have a top level repository with plenty of git submodules. I wanted to specify a common bug tracker rule in the" root" repository that is automatically applied to all submodules, unfortunately there exists no such option.

So my request would be to add the possibility to specify common bug tracker rules in the global/branch settings, or, if you thing that would be to generic, an option to take over rules from a "root" repository into submodules. It could also be implement so that there is a checkbox and once checked the .issuetracker file is copied/merged down into the submodules after creating/updating the the rules.

BR, Karsten

Adanteh commented 3 years ago

Would appreciate this as well.

dsbert commented 3 years ago

Another possibility is tying these settings to the workspace instead of making it global or per repository.

Schtorsk commented 2 years ago

I would also love to put a global .issuetracker in %localappdata%/Fork just like it already reads the global custom-commands.json that is in this folder!