Skip to content

Conversation

@mpnowacki-reef
Copy link
Contributor

No description provided.


### 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

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

Successfully merging this pull request may close these issues.

3 participants