Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change default support link #42

Open
Aniruddha-Shriwant opened this issue Apr 12, 2021 · 2 comments
Open

Change default support link #42

Aniruddha-Shriwant opened this issue Apr 12, 2021 · 2 comments

Comments

@Aniruddha-Shriwant
Copy link
Contributor

Feature Request 🛍️

Use Case

When the add-in has some problem or if a user gets any problem with the add-in, the user will click on the get support option here
Scenario 1: When the add-in is working properly, but the user notices some error
image
Scenario 2: when the add-in gets the error
image

but currently, we have contoso.com/help as the default support link

<SupportUrl DefaultValue="https://www.contoso.com/help"/>

Also, https://www.contoso.com/help redirects to https://www.microsoft.com/en-us so the user might get confused about where to get the support

Possible Solution

A possible solution will be to redirect the user to this link:
https://github.com/accordproject/cicero-word-add-in/issues/new?assignees=&labels=&template=custom-issue.md&title=
So that he can create an issue on GitHub and then maintainers can help him...
I was also thinking of pointing the user to some FAQ's where he might get his queries resolved but currently, we are not having any documentation hence pointing the user to create an issue would be better

I would like to make PR for this if this is a valid issue :)

@algomaster99
Copy link
Member

You can submit a PR for this.

@Aniruddha-Shriwant
Copy link
Contributor Author

As I had suggested that we may point the user to the create issue link because as of now we are not having any documentation or any FAQ's for Add-in ( I would also like to work on this afterward)

So, I was thinking of a custom-issue template and bug-report template link but then there are some heading like Possible solution / Possible implementation which normal add-in user should not bother about, also we may need to know the Word Version as this is never asked in those templates but we may need that here

So I was thinking to create a new issue template for this that would look similar to this

Bug Report 🐛

Expected Behavior

Current Behavior

Steps to Reproduce

Context (Environment)

Desktop

  • OS: [e.g. macOS]
  • Browser: [e.g. Chrome, Safari]
  • Browser's Version: [e.g. 0.22.15]
  • MS Word Version : [e.g 16.0]

If we don't think there is a need for this new issue-template then maybe we can just update bug-report.md and include MS word version in Desktop Environment

@algomaster99 can you share your thoughts on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants