Make brewers friend issue tracker available to members?

[steinmb]

I think it would benefit the community if the issue tracker was made public to paying members. Currently forum posts is getting answered by staff and then some of them ends up as a technical issue but after that we get no issue number and link allowing us to follow up on the issue, provide more technical information, etc.

There is also a mix of issues that are not bugs turn into feature request with often even longer timeline, and they are even harder to track the progress of.

https://opensource.com/open-organization/17/2/tracking-issues-publicly

 

[Pricelessbrewing]

We've talked about this a number of times and the development team and owners are on board.

We just need to figure out an easy method of integration that 1) Doesn't expose the code 2) allows for internal private communication as well as external customer facing and 3) Allows for accessible user interaction without users having to make a separate account on github/bitbucket etc as the majority of our users are not familiar with software development and don't want to force yet another account onto them.

If anyone watching is familiar with anything that satisfies those 3 needs, ideally with the ability for customers to vote Up/Down issues.

 

[Donoroto]

We've talked about this a number of times and the development team and owners are on board.

We just need to figure out an easy method of integration that 1) Doesn't expose the code 2) allows for internal private communication as well as external customer facing and 3) Allows for accessible user interaction without users having to make a separate account on github/bitbucket etc as the majority of our users are not familiar with software development and don't want to force yet another account onto them.

If anyone watching is familiar with anything that satisfies those 3 needs, ideally with the ability for customers to vote Up/Down issues.

In a similar situation, we decided to maintain an independent spreadsheet for our public-facing issue tracking. Not highly featured, and a minor task to maintain, but effective in communicating issue numbers and status.

 

[steinmb]

Gitlab/github etc all have a REST API allowing 3-part application pulling data from it. Perhaps the least intrusive change would be a to integrate this forum with that? Even a quick semi-manual integration would make the changes and issues less a block box for us paying customers. Example MVP:

1. A forum post is created.
2. This turn into be a real bug.
3. Manually create a issue at, example: Github/Gitlab.
4. Forum moderator have a ability to add the issue number to the forum issue.
5. Linking to a issue allow your custom integration allow the forum to pull inn wanted information like issue title, tags, comment, status, milestone etc.

Safe your you guys. Only allowing the forum (client) reading from the API, but also control what request it can do, example - only issues etc.

 

[Yooper]

Gitlab/github etc all have a REST API allowing 3-part application pulling data from it. Perhaps the least intrusive change would be a to integrate this forum with that? Even a quick semi-manual integration would make the changes and issues less a block box for us paying customers. Example MVP:

1. A forum post is created.
2. This turn into be a real bug.
3. Manually create a issue at, example: Github/Gitlab.
4. Forum moderator have a ability to add the issue number to the forum issue.
5. Linking to a issue allow your custom integration allow the forum to pull inn wanted information like issue title, tags, comment, status, milestone etc.

Safe your you guys. Only allowing the forum (client) reading from the API, but also control what request it can do, example - only issues etc.

@Pricelessbrewing
I think this could be something that might work for us- what do you think? Not sure how #4 would/could work with our procedure, but I think we should discuss.

 

[Donoroto]

@Pricelessbrewing
I think this could be something that might work for us- what do you think? Not sure how #4 would/could work with our procedure, but I think we should discuss.

You can't change the thread title? Ok, if not, just reply to the original post describing the issue with a tracking number. Simple yet functional, albeit highly manual.