Open
Conversation
|
|
||
| ### 6.6 Jira and Notion | ||
|
|
||
| We use Jira to track work items, current, past and future. Tasks in Jira should be described properly so that any person in given project can pick it up and start working. the Description should be placed in the jira task itself if it's not very big and is self contained. If the task is a part of a larger design/algorthm/feature set then the full description should be placed in Notion. Individual task(s) related to that should then make it clear which part of the design is supposed to be considered when working on that task and the description should have a link to Notion. It is our joint responsibility to make sure jira issues are described that way - centralising that burden on a single person is not good for the state of tasks or for the culture in general. So follow these rules whne creating tasks and act when you find ones not adhering to these rules. |
Contributor
There was a problem hiding this comment.
Suggested change
| We use Jira to track work items, current, past and future. Tasks in Jira should be described properly so that any person in given project can pick it up and start working. the Description should be placed in the jira task itself if it's not very big and is self contained. If the task is a part of a larger design/algorthm/feature set then the full description should be placed in Notion. Individual task(s) related to that should then make it clear which part of the design is supposed to be considered when working on that task and the description should have a link to Notion. It is our joint responsibility to make sure jira issues are described that way - centralising that burden on a single person is not good for the state of tasks or for the culture in general. So follow these rules whne creating tasks and act when you find ones not adhering to these rules. | |
| We use Jira to track work items, current, past and future. Tasks in Jira should be described properly so that any person in given project can pick it up and start working. the Description should be placed in the jira task itself if it's not very big and is self contained. If the task is a part of a larger design/algorthm/feature set then the full description should be placed in Notion. Individual task(s) related to that should then make it clear which part of the design is supposed to be considered when working on that task and the description should have a link to Notion. It is our joint responsibility to make sure jira issues are described that way - centralising that burden on a single person is not good for the state of tasks or for the culture in general. So follow these rules when creating tasks and act when you find ones not adhering to these rules. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.