# data[].attributes.body
Splitting files more, would give much more flexibility in change them without impacting the other code.

# data[].attributes.body
using the Single responsibility principle more in our code base

# data[].attributes.body
How is doing auto documentation, and how do we do it.

# data[].attributes.body
Find a way of extracting data from jira, to be used for graphs, if we like them specilised.

# data[].attributes.body
To minimize work need to create demo powerpoint, jira internal graph should be use.

# data[].attributes.body
We are not waiting on people, all is fine

# data[].attributes.body
Test on multiple branches is slow. This can be speed up using virtual machines.
We need to find a way of doing this with 3D models.

# data[].attributes.body
When moving into git, we will desiged when we update to new nuges.

# data[].attributes.body
3DD is slow to test on, but CAM Client is not aligned with full mode.
Fix this and the working environment will be much better

# data[].attributes.body
We need specification on the machines

# data[].attributes.headline
Look at bug in backlook at make sure there are still bugs

# data[].attributes.subject
Look at bug in backlook at make sure there are still bugs

# data[].attributes.body
We have 46 bug in our backlog and 17 in bugzilla.
We should have close them or fix them.

# data[].attributes.body
Add unit test to all new code that are added in our solution.
Do unit test of original core funtionality.

# data[].attributes.body
Make our view modes testeable. So we can make UI test on CAM in a fast and easy way.

# data[].attributes.body
The CAM server is not tested wery well at the moment.
This could be done by using the Rest API.
A simple framwork for doing this test should be look into

# data[].attributes.headline
Define what Test should be covered by white testing.

# data[].attributes.subject
Define what Test should be covered by white testing.

# data[].attributes.body
Defining what should be tested by white test.
Collaboration between tester and developer to get it all up and running correctly.

# data[].attributes.body
1 hour

# data[].attributes.body
1 hour

# data[].attributes.body
1 hour

# data[].attributes.body
4 days times 1/2 per release candidat

# data[].attributes.body
1 hour - 1 Day and 1 hour

# data[].attributes.body
1 Hour

# data[].attributes.body
1 hour

# data[].attributes.body
1 hour

# data[].attributes.body
1 Hour

# data[].attributes.body
3 days

# data[].attributes.headline
Create release protocol and define documents to be corrected

# data[].attributes.subject
Create release protocol and define documents to be corrected

# data[].attributes.body
1 Hour

# data[].attributes.body
1 hour

# data[].attributes.body
30 min

# data[].attributes.body
30 min - 1 day

# data[].attributes.body
0 Hours

# data[].attributes.body
2 hours

# data[].attributes.body
8 days and 3 hour

# data[].attributes.body
Write task description

# data[].attributes.body
1 hour

# data[].attributes.body
7 hours

# data[].attributes.body
7 days

# data[].attributes.body
1 Hour

# data[].attributes.body
6 Hours

# data[].attributes.body
1 Hour

# data[].attributes.body
2 Hour

# data[].attributes.body
1 Hour