• Inbox tracking
• Bugs to be verified
• Verification needed

Every week one of the teammates triage new issues and pull requests submitted by the community.

The inbox tracker should do followings:

• Is the issue invaid? Close it and assign invalid label with justifying the reason.
• Is the issue a general question, like How can I run the Bot? Close it and assign question label redirecting the owner to Stack Overflow with this message:

Please ask `how-to` questions about JIRA Journal on [Stack Overflow](https://stackoverflow.com/questions/tagged/jira-journal) using
the tag `jira-journal`.

The JIRA Journal team together with the JIRA Journal Community will answer your question over there.

• Else, assign the issue to the owner of a feature area.

Everyone should do following to their assigned issues:

• If the issue need more info, assign need-more-info label and ask for more information in a comment.
• Ensure the issue has a type label assigned, i.e. bug, feature-request, need-more-info, debt.
• Ensure the issue has a feature area label, and optionally a sub area label assigned. See Feature Areas.
• Do your utmost to identify duplicates.
• Is the issue a duplicate? Close it and assign duplicate label with the original issue # in a comment.
• If the issue is a feature request, assign feature-request label.
• If the issue is an important bug, assign important label.
• If the issue needs to be fixed in this release, assign it to the current milestone (blocks a scenario, completes a new feature, etc.).

• JIRA Journal team monitor feature requests.
• Feature requests are assigned to On Plate milestone. Our goal is to keep it under 100 issues.

• We must verify all the issues.
• Implecity verify all issues labled as bug.
• Explicitly request to verify issues with verification-needed label.

Find issues that are to be verified with these queries:

• Bugs to be verified
• Verification needed issues

Follow these rules:

1. Query issues that requires verification.
2. Start with your own issues but not closed.
3. Pick an item.

• Assign verified label when you start.
• Verify the issue.
• If the issue still shows, replace verified label with verification-found label.
• Go back to #3.

We use issues for iteration planning with the label iteration-plan and a list of [ ] tasks for different items for each erea:

• Important Dates
• Plan Items for performance, feedback, debt, adoption, engineering, exploration.
• Bugs

During iteration planning:

• The On Plate backlog is groomed.
• Review features with many reactions.
• Assign issues to the current milestone.