Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2024-11-11 01:54:40 +08:00
Code Issues Projects Releases Packages Wiki Activity
Mailspring/ISSUE_TEMPLATE.md

55 lines
1.6 KiB
Markdown
Raw Normal View History

:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
<!--
Add a note to the ISSUE_TEMPLATE asking for mailsync logs
2018-08-03 03:46:52 +08:00
Thanks for taking the time to file an issue! The Mailspring community uses GitHub issues to coordinate development.
:art:(rename): Update Nylas N1 to Nylas Mail Test Plan: Tested locally. Reviewers: halla, juan, evan Reviewed By: juan, evan Differential Revision: https://phab.nylas.com/D3645
2017-01-12 09:41:07 +08:00
Link to the new Slack channel from GitHub
2017-10-18 00:29:23 +08:00
If you have question about Mailspring or a problem with your email account, search the Knowledge Base to see if it's addressed there. If it's not, join our Slack organization and ask the community:
:art:(rename): Update Nylas N1 to Nylas Mail Test Plan: Tested locally. Reviewers: halla, juan, evan Reviewed By: juan, evan Differential Revision: https://phab.nylas.com/D3645
2017-01-12 09:41:07 +08:00
Link to the new Slack channel from GitHub
2017-10-18 00:29:23 +08:00
- http://support.getmailspring.com/hc/en-us/
- https://join-mailspring-slack.herokuapp.com/
Our team tries to respond to all GitHub issues. To make sure your issue is actionable, try to include the following information:
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
-->
gh: Initial commit of issue template
2016-02-19 01:55:52 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
##### Are there any related issues?
Add a note to the ISSUE_TEMPLATE asking for mailsync logs
2018-08-03 03:46:52 +08:00
Switch product name to “Mailspring”
2017-09-06 04:37:40 +08:00
<!-- Try searching for both open and closed issues here: https://github.com/Foundry376/Mailspring/issues?q=is%3Aissue. Keep in mind that email features are often described differently on different platforms. (Conversations == threads, shortcuts == hotkeys, etc.) -->
Add a note to the ISSUE_TEMPLATE asking for mailsync logs
2018-08-03 03:46:52 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
...
gh: Issue template isn't actually displayed as markdown
2016-02-19 02:03:18 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
##### What operating system are you using?
Add a note to the ISSUE_TEMPLATE asking for mailsync logs
2018-08-03 03:46:52 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
...
gh: Issue template isn't actually displayed as markdown
2016-02-19 02:03:18 +08:00
Switch product name to “Mailspring”
2017-09-06 04:37:40 +08:00
##### What version of Mailspring are you using?
Add a note to the ISSUE_TEMPLATE asking for mailsync logs
2018-08-03 03:46:52 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
...
gh: Issue template isn't actually displayed as markdown
2016-02-19 02:03:18 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
--
gh: Initial commit of issue template
2016-02-19 01:55:52 +08:00
fix(issue-template): Update formatting
2016-02-19 03:05:13 +08:00
**Bug?**
Add a note to the ISSUE_TEMPLATE asking for mailsync logs
2018-08-03 03:46:52 +08:00
##### Is this an email sync or connection issue?
<!-- If you're having trouble syncing an account, please zip and attach Mailspring's sync
logs to your issue. From the app's menu, choose Developer > Show Mailsync Logs.
The mailsync-**.log files contain very little PII and lots of debug info! -->
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
...
gh: Initial commit of issue template
2016-02-19 01:55:52 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
##### Is the issue related to a specific email provider (Gmail, Exchange, etc.)?
Add a note to the ISSUE_TEMPLATE asking for mailsync logs
2018-08-03 03:46:52 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
...
gh: Issue template isn't actually displayed as markdown
2016-02-19 02:03:18 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
##### Is the issue reproducible with a particular attachment, message, signature, etc?
Add a note to the ISSUE_TEMPLATE asking for mailsync logs
2018-08-03 03:46:52 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
<!-- Try to provide an example as a file attachment or a screenshot. -->
Add a note to the ISSUE_TEMPLATE asking for mailsync logs
2018-08-03 03:46:52 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
...
gh: Initial commit of issue template
2016-02-19 01:55:52 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
--
gh: Initial commit of issue template
2016-02-19 01:55:52 +08:00
fix(issue-template): Update formatting
2016-02-19 03:05:13 +08:00
**Feature Request?**
Add a note to the ISSUE_TEMPLATE asking for mailsync logs
2018-08-03 03:46:52 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
##### Does this feature exist in another mail client or tool you use?
Add a note to the ISSUE_TEMPLATE asking for mailsync logs
2018-08-03 03:46:52 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
...
Reference in a new issue Copy permalink