integrations / microsoft-teams

Bringing your code and work to the conversations you care about with the GitHub and Microsoft integration
443 stars 97 forks source link

Unable to view Lists of all reported Issues, also unable to refer to a specific issue with help of a # number and add comments directly to it. #147

Open rxa1031 opened 3 years ago

rxa1031 commented 3 years ago

Hello,

With this GitHub bot / app I am unable to fetch list of all reported issues. There is no command listed for it.

The command @github subscribe list features only helps to know what features are subscribed issues, pulls, commits:'*', comments.

There is no commands similar to any one of @github list issues open, @github list issues closed, @github list issues all.

As a result of above my team dislikes using this GitHub bot / App. They also dislike searching for the issue that they want to add information too. The issue could be months old, and one has to scroll up in the channel to find it.

They rater like UNITO tool more, we have used it in past along with Wrike and it used to create a separate line for every reported issue.

Also refer to #145

Please provide immediate solution, as I need to share it ASAP with my Team.

Thanks, @rxa1031

rxa1031 commented 3 years ago

I need to share a simple solution with them (one that is not too technical). There could be technicians or end user who would want to report an issue.

gauravsaralMs commented 3 years ago

With this GitHub bot / app I am unable to fetch list of all reported issues. There is no command listed for it.

Feature request, not a bug

ashokirla commented 3 years ago

@rxa1031 Thanks for the feedback. We have this support planned in your backlog. With this feature you can list issues, create and manage issues through various commands.

Please let me know if you are interested in having a call. I would to share our proposal get your feedback.

rxa1031 commented 3 years ago

Hello @ashokirla ,

My time-zone is IST. What time can we have a meting on Monday?

I am not aware how to share my email ID securely with you.

Zoom call would be preferable.

Please suggest.

Thanks, @rxa1031

rxa1031 commented 3 years ago

Hello @ashokirla ,

I shared below information over call with you:

COMMITS (existing):

GitHub date Company/Project 1 new commit to XXX by @rrr nnnnn What changed

ISSUES (Existing):

Company/Project Issue opened by @rrr on date

Issue Heading

Issue Status

Text / information

Assignees: ... Labels: ...

Tools used in past:

My team mates have used below in past. They liked the ISSUE LIST view in Wrike: https://guide.unito.io/en/articles/3478431-wrike-github-integration

Please check the below page and the video on the page: https://unito.io/integrations/wrike-github/

WRIKE + UNITO + GITHUB scenario:

Main Project |--> Task 1 |--> Task 2 |--> XXX Project Issues (Close / Open / ...) ^^^^^|--> Issue 01 ^^^^^|--> Issue 02 ^^^^^|--> Issue 03 ^^^^^|--> Issue 04 ...

Used ^ for alignment as the space could not be added.

Please share your inputs.

Thanks, Rajeev

rxa1031 commented 3 years ago

In WRIKE, we used to use the Right side pane which showed an Issues Task. Within the issues Task we were able to select what type of issues we want to view, like All, open, closed, etc. We would then click the SUB-TASK to which we either want to update information (including file attachments) or review information and then take actions (within the specific Issue sub-task) as needed.

The GitHub bot does not work inside a Private repository. It therefore becomes difficult to hide certain developments from other viewers.

rxa1031 commented 3 years ago

Is it possible somehow to add the GitHub bot to the Private channels as well, so that people who are part of the channel can only get information fetched by the GitHub bot. Can the GitHub bot be somehow added as a user to mitigate the current limitation (with private channel, which does not exist with public channel?

rxa1031 commented 2 years ago

Hello @ashokirla ,

What is the current released version for the App. It (appears) that the version that I am using is 1.3.

Is there an update on the progress of this issue?

Regards, Rajeev