How to properly organize ISSUE maintenance in a project?

Question

git

We need before we redirect.
Write down exactly what was done. (At the same time, the task already describes what needs to be done)
Give a link where to look.
Give the commit number. (In the commit, you need to describe what you did in the comment)
Give a picture with which you can compare. (If layout)
Put needcheck.
Redirect.
At the end of the day, write down in detail what was done during the day.
Is this NORM?

Answer 1

In general, I think that this is the norm.
For the case of 1 developer and 1 manager, this is really a kind of overhead, but there is an important point: if you don’t get used to such a process NOW, you won’t be able to instantly switch to it when you need it .
In addition, strict reporting helps to better plan your own time and objectively evaluate deadlines.
Point by point below:

Write down exactly what was done. (At the same time, the task already outlines what needs to be done)

It really depends on how detailed your tasks are.
Of course, you don’t need to bring it to insanity, but some additional implementation details will never hurt. However, this is quite possible to write in messages to the pull request.

Give a link where to look.

Always a must!

Give the commit number. (In the commit you need to describe what you did in the comment)

Many systems, such as jira, are great friends with repositories and automatically collect changelog from commit comments. At the same time, time is also taken into account.
Live picture joxi.ru/1XToU_3JTJBuefeWz0o

Give a picture with which to compare. (If layout)

Necessarily

Put needcheck.

It's also logical.
Personally, it's more convenient for me to do it with task statuses
To Do <-> In Progress <-> Testing <-> Done,
but this is subjective.

At the end of the day, write down in detail what was done during the day.

If the tasks are completely closed before the end of the working day, this is, in principle, redundant, you can look at the commits. If the tasks are long - this is a must.
I still make you usually write what you plan to do the next day.

Answer 2

This is quite a good norm, commits can be integrated with the tasktracker and they themselves will fall into the task by its number.
And so everything seems to be fine with you and it’s not clear where such questions come from?
Apparently you have some kind of problem, but you forgot to voice it?

Answer 3

I think it's hell