dmitriy.kazimirov/assayo
1
0
Fork 0
mirror of https://github.com/bakhirev/assayo.git synced 2024-11-16 16:21:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

update

Browse source
This commit is contained in:
bakhirev 2024-07-17 17:53:43 +03:00
parent ca41512927
commit 8ba48ca077
22 changed files with 156 additions and 80 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
build/static/index.css
View file

File diff suppressed because one or more lines are too long

6
build/static/index.js
View file

File diff suppressed because one or more lines are too long

1
src/ts/components/Recommendations/styles/modal.module.scss
View file

@ -20,6 +20,7 @@
font-weight: 100;
font-size: var(--font-s);
margin: var(--space-xs) 0 0 0;
line-height: 1.5;
color: var(--color-black);
}

6
src/ts/components/Tempo/components/Tasks.tsx
View file

@ -1,4 +1,5 @@
import React from 'react';
import { useTranslation } from 'react-i18next';
import ICommit from 'ts/interfaces/Commit';
import IHashMap from 'ts/interfaces/HashMap';
@ -41,6 +42,7 @@ interface ITaskProps {
}
function Task({ title, commits }: ITaskProps) {
const { t } = useTranslation();
const prId = dataGrip.pr.prByTask[title];
return (
<div
@ -67,7 +69,7 @@ function Task({ title, commits }: ITaskProps) {
</figcaption>
</figure>
<figcaption className={style.tempo_task_title}>
Коммиты
{t('page.team.day.commits')}
</figcaption>
</figure>
<figure className={style.tempo_task_hours}>
@ -81,7 +83,7 @@ function Task({ title, commits }: ITaskProps) {
</figcaption>
</figure>
<figcaption className={style.tempo_task_title}>
Активность
{t('page.team.day.activity')}
</figcaption>
</figure>
</div>

12
src/ts/helpers/DataGrip/components/pr.ts
View file

@ -106,12 +106,12 @@ export default class DataGripByPR {
static getPRByGroups(list: any, propertyName: string) {
const TITLES = {
DAY: 'день',
THREE_DAY: 'три дня',
WEEK: 'неделя',
TWO_WEEK: 'две недели',
MONTH: 'месяц',
MORE: 'более',
DAY: 'page.team.pr.chart.1day',
THREE_DAY: 'page.team.pr.chart.3day',
WEEK: 'page.team.pr.chart.7day',
TWO_WEEK: 'page.team.pr.chart.14day',
MONTH: 'page.team.pr.chart.30day',
MORE: 'page.team.pr.chart.more',
};
const details = {

23
src/ts/pages/Team/components/PR/Authors.tsx
View file

@ -9,16 +9,6 @@ import LineChart from 'ts/components/LineChart';
import getOptions from 'ts/components/LineChart/helpers/getOptions';
import { getMax } from 'ts/pages/Common/helpers/getMax';
const TITLES = {
DAY: 'день',
THREE_DAY: 'три дня',
WEEK: 'неделя',
TWO_WEEK: 'две недели',
MONTH: 'месяц',
MORE: 'более',
};
const order = Object.values(TITLES);
interface IAuthorsProps {
response?: IPagination<any>;
updateSort?: Function;
@ -29,7 +19,18 @@ interface IAuthorsProps {
function Authors({ response, updateSort, rowsForExcel, mode }: IAuthorsProps) {
if (!response) return null;
const timeChart = getOptions({ order, limit: 3 });
const timeChart = getOptions({
order: [
'page.team.pr.chart.1day',
'page.team.pr.chart.3day',
'page.team.pr.chart.7day',
'page.team.pr.chart.14day',
'page.team.pr.chart.30day',
'page.team.pr.chart.more',
],
limit: 3,
});
const weightedAverageChart = getOptions({
max: getMax(response, 'weightedAverage'),
order: [

8
src/ts/translations/de/pages.ts
View file

@ -107,6 +107,8 @@ export default `
§ page.team.tree.linesAdded: added
§ page.team.tree.linesChanged: changed
§ page.team.tree.linesRemoved: removed
§ page.team.day.commits: Commits
§ page.team.day.activity: Activity
§ page.team.week.title: Weekly statistics
§ page.team.week.date: Date
§ page.team.week.numberTasks: Number of tasks
@ -128,6 +130,12 @@ export default `
§ page.team.pr.workDays: Development days
§ page.team.pr.delayDays: Days waiting for merge
§ page.team.pr.middleTimeRelease: Average delivery time (days)
§ page.team.pr.chart.1day: day
§ page.team.pr.chart.3day: three days
§ page.team.pr.chart.7day: week
§ page.team.pr.chart.14day: two weeks
§ page.team.pr.chart.30day: month
§ page.team.pr.chart.more: more
§ page.team.pr.commits: Commits
§ page.team.pr.date: Merge Date
§ page.team.pr.mergeAuthor: Merged by

16
src/ts/translations/de/recommendations.ts
View file

@ -25,7 +25,7 @@ working on weekends
- employees burn out faster;
§ recommendations.timestamp.regularWeekendWord.title: Regular Overtime
§ recommendations.timestamp.sometimeWeekendWord.title: Occasional Overtime
§ recommendations.timestamp.sometimeWeekendWord.title: Occasional overtime
§ recommendations.timestamp.weekendWord.description
It might be advisable to change the project manager, analyst, and architect.
@ -52,7 +52,7 @@ But sometimes it happens.
- employees burn out faster;
§ recommendations.scope.parallelism.not.title
No Parallel Work
No parallel work
§ recommendations.scope.parallelism.not.description
any feature at any given time is done by one person.
@ -136,7 +136,7 @@ one person is deeply involved in a feature.
- more than 80% of commits in a feature are made by one person;
§ recommendations.scope.types.process.title
Poor Processes
Poor processes
§ recommendations.scope.types.process.description
Most features contain one type of task.
@ -165,7 +165,7 @@ It's possible that developers are incorrectly signing commits or the manager is
- style revisions (as a result of focus group feedback);
§ recommendations.scope.plan.title
Develop a Long-Term Plan
Develop a long-term plan
§ recommendations.scope.plan.description
taking architecture into account.
@ -426,7 +426,7 @@ or tasks are poorly split. Need to check. If granularity is the same - take cont
- tasks could have been more complex than they seemed;
- tasks could have had a large volume of work (need to check if the number of changes is also decreasing during this period)
§ recommendations.type.everyHasOne.title: Not Signing Task Types
§ recommendations.type.everyHasOne.title: Not signing task types
§ recommendations.type.everyHasOne.description: Most task types are done by one person.
§ recommendations.type.oneMaintainer.title: Narrow Specialization
§ recommendations.type.oneMaintainer.description
@ -458,7 +458,7 @@ How to fix this:
- change the area of work (tests, documentation, bugs) among employees every sprint;
§ recommendations.type.fewTypes.title
This is a Local Product
This is a local product
§ recommendations.type.fewTypes.description
for a specific customer or problem.
@ -481,7 +481,7 @@ In this case, we see a small number of types, which likely indicates shortcoming
Based on file types, we can assume the type of program (website, server application, DevOps scripts, etc.). For a frontend application, our hypothesis will be more accurate than for DevOps scripts, which might just be a micro-module of initialization.
§ recommendations.type.diff.title
Break Down the Leading Type into Subtypes
Split the popular type into subtypes
§ recommendations.type.diff.description
to detail errors.
@ -496,7 +496,7 @@ Consider several options for subtypes:
- fix (error detected in production);
§ recommendations.type.buddy.title
Accumulate Minor Tasks
Accumulate minor tasks
§ recommendations.type.buddy.description
for new employees.

8
src/ts/translations/en/pages.ts
View file

@ -107,6 +107,8 @@ export default `
§ page.team.tree.linesAdded: added
§ page.team.tree.linesChanged: changed
§ page.team.tree.linesRemoved: removed
§ page.team.day.commits: Commits
§ page.team.day.activity: Activity
§ page.team.week.title: Weekly statistics
§ page.team.week.date: Date
§ page.team.week.numberTasks: Number of tasks
@ -130,6 +132,12 @@ export default `
§ page.team.pr.all.workDays: Time spent working on a task
§ page.team.pr.all.delayDays: Time of the PR review
§ page.team.pr.middleTimeRelease: The ratio of development time to review time
§ page.team.pr.chart.1day: day
§ page.team.pr.chart.3day: three days
§ page.team.pr.chart.7day: week
§ page.team.pr.chart.14day: two weeks
§ page.team.pr.chart.30day: month
§ page.team.pr.chart.more: more
§ page.team.pr.commits: Commits
§ page.team.pr.date: Merge Date
§ page.team.pr.mergeAuthor: Merged by

16
src/ts/translations/en/recommendations.ts
View file

@ -25,7 +25,7 @@ working on weekends
- employees burn out faster;
§ recommendations.timestamp.regularWeekendWord.title: Regular Overtime
§ recommendations.timestamp.sometimeWeekendWord.title: Occasional Overtime
§ recommendations.timestamp.sometimeWeekendWord.title: Occasional overtime
§ recommendations.timestamp.weekendWord.description
It might be advisable to change the project manager, analyst, and architect.
@ -52,7 +52,7 @@ But sometimes it happens.
- employees burn out faster;
§ recommendations.scope.parallelism.not.title
No Parallel Work
No parallel work
§ recommendations.scope.parallelism.not.description
any feature at any given time is done by one person.
@ -136,7 +136,7 @@ one person is deeply involved in a feature.
- more than 80% of commits in a feature are made by one person;
§ recommendations.scope.types.process.title
Poor Processes
Poor processes
§ recommendations.scope.types.process.description
Most features contain one type of task.
@ -165,7 +165,7 @@ It's possible that developers are incorrectly signing commits or the manager is
- style revisions (as a result of focus group feedback);
§ recommendations.scope.plan.title
Develop a Long-Term Plan
Develop a long-term plan
§ recommendations.scope.plan.description
taking architecture into account.
@ -426,7 +426,7 @@ or tasks are poorly split. Need to check. If granularity is the same - take cont
- tasks could have been more complex than they seemed;
- tasks could have had a large volume of work (need to check if the number of changes is also decreasing during this period)
§ recommendations.type.everyHasOne.title: Not Signing Task Types
§ recommendations.type.everyHasOne.title: Not signing task types
§ recommendations.type.everyHasOne.description: Most task types are done by one person.
§ recommendations.type.oneMaintainer.title: Narrow Specialization
§ recommendations.type.oneMaintainer.description
@ -458,7 +458,7 @@ How to fix this:
- change the area of work (tests, documentation, bugs) among employees every sprint;
§ recommendations.type.fewTypes.title
This is a Local Product
This is a local product
§ recommendations.type.fewTypes.description
for a specific customer or problem.
@ -481,7 +481,7 @@ In this case, we see a small number of types, which likely indicates shortcoming
Based on file types, we can assume the type of program (website, server application, DevOps scripts, etc.). For a frontend application, our hypothesis will be more accurate than for DevOps scripts, which might just be a micro-module of initialization.
§ recommendations.type.diff.title
Break Down the Leading Type into Subtypes
Split the popular type into subtypes
§ recommendations.type.diff.description
to detail errors.
@ -496,7 +496,7 @@ Consider several options for subtypes:
- fix (error detected in production);
§ recommendations.type.buddy.title
Accumulate Minor Tasks
Accumulate minor tasks
§ recommendations.type.buddy.description
for new employees.

8
src/ts/translations/es/pages.ts
View file

@ -107,6 +107,8 @@ export default `
§ page.team.tree.linesAdded: agregaron
§ page.team.tree.linesChanged: changed
§ page.team.tree.linesRemoved: cambiaron
§ page.team.day.commits: Commits
§ page.team.day.activity: Activity
§ page.team.week.title: Estadísticas semanales
§ page.team.week.date: Fecha
§ page.team.week.numberTasks: Número de tareas
@ -130,6 +132,12 @@ export default `
§ page.team.pr.all.workDays: Time spent working on a task
§ page.team.pr.all.delayDays: Time of the PR review
§ page.team.pr.middleTimeRelease: The ratio of development time to review time
§ page.team.pr.chart.1day: day
§ page.team.pr.chart.3day: three days
§ page.team.pr.chart.7day: week
§ page.team.pr.chart.14day: two weeks
§ page.team.pr.chart.30day: month
§ page.team.pr.chart.more: more
§ page.team.pr.commits: commits
§ page.team.pr.date: Date of injection
§ page.team.pr.mergeAuthor: I poured it in

16
src/ts/translations/es/recommendations.ts
View file

@ -25,7 +25,7 @@ working on weekends
- employees burn out faster;
§ recommendations.timestamp.regularWeekendWord.title: Regular Overtime
§ recommendations.timestamp.sometimeWeekendWord.title: Occasional Overtime
§ recommendations.timestamp.sometimeWeekendWord.title: Occasional overtime
§ recommendations.timestamp.weekendWord.description
It might be advisable to change the project manager, analyst, and architect.
@ -52,7 +52,7 @@ But sometimes it happens.
- employees burn out faster;
§ recommendations.scope.parallelism.not.title
No Parallel Work
No parallel work
§ recommendations.scope.parallelism.not.description
any feature at any given time is done by one person.
@ -136,7 +136,7 @@ one person is deeply involved in a feature.
- more than 80% of commits in a feature are made by one person;
§ recommendations.scope.types.process.title
Poor Processes
Poor processes
§ recommendations.scope.types.process.description
Most features contain one type of task.
@ -165,7 +165,7 @@ It's possible that developers are incorrectly signing commits or the manager is
- style revisions (as a result of focus group feedback);
§ recommendations.scope.plan.title
Develop a Long-Term Plan
Develop a long-term plan
§ recommendations.scope.plan.description
taking architecture into account.
@ -426,7 +426,7 @@ or tasks are poorly split. Need to check. If granularity is the same - take cont
- tasks could have been more complex than they seemed;
- tasks could have had a large volume of work (need to check if the number of changes is also decreasing during this period)
§ recommendations.type.everyHasOne.title: Not Signing Task Types
§ recommendations.type.everyHasOne.title: Not signing task types
§ recommendations.type.everyHasOne.description: Most task types are done by one person.
§ recommendations.type.oneMaintainer.title: Narrow Specialization
§ recommendations.type.oneMaintainer.description
@ -458,7 +458,7 @@ How to fix this:
- change the area of work (tests, documentation, bugs) among employees every sprint;
§ recommendations.type.fewTypes.title
This is a Local Product
This is a local product
§ recommendations.type.fewTypes.description
for a specific customer or problem.
@ -481,7 +481,7 @@ In this case, we see a small number of types, which likely indicates shortcoming
Based on file types, we can assume the type of program (website, server application, DevOps scripts, etc.). For a frontend application, our hypothesis will be more accurate than for DevOps scripts, which might just be a micro-module of initialization.
§ recommendations.type.diff.title
Break Down the Leading Type into Subtypes
Split the popular type into subtypes
§ recommendations.type.diff.description
to detail errors.
@ -496,7 +496,7 @@ Consider several options for subtypes:
- fix (error detected in production);
§ recommendations.type.buddy.title
Accumulate Minor Tasks
Accumulate minor tasks
§ recommendations.type.buddy.description
for new employees.

8
src/ts/translations/fr/pages.ts
View file

@ -107,6 +107,8 @@ export default `
§ page.team.tree.linesAdded: ajoutâtes
§ page.team.tree.linesChanged: changed
§ page.team.tree.linesRemoved: modifiâtes
§ page.team.day.commits: Commits
§ page.team.day.activity: Activity
§ page.team.week.title: Statistiques par semaine
§ page.team.week.date: Date
§ page.team.week.numberTasks: Nombre de tâches
@ -130,6 +132,12 @@ export default `
§ page.team.pr.all.workDays: Time spent working on a task
§ page.team.pr.all.delayDays: Time of the PR review
§ page.team.pr.middleTimeRelease: The ratio of development time to review time
§ page.team.pr.chart.1day: day
§ page.team.pr.chart.3day: three days
§ page.team.pr.chart.7day: week
§ page.team.pr.chart.14day: two weeks
§ page.team.pr.chart.30day: month
§ page.team.pr.chart.more: more
§ page.team.pr.commits: Commits
§ page.team.pr.date: Date de diffusion
§ page.team.pr.mergeAuthor: Versai

16
src/ts/translations/fr/recommendations.ts
View file

@ -25,7 +25,7 @@ working on weekends
- employees burn out faster;
§ recommendations.timestamp.regularWeekendWord.title: Regular Overtime
§ recommendations.timestamp.sometimeWeekendWord.title: Occasional Overtime
§ recommendations.timestamp.sometimeWeekendWord.title: Occasional overtime
§ recommendations.timestamp.weekendWord.description
It might be advisable to change the project manager, analyst, and architect.
@ -52,7 +52,7 @@ But sometimes it happens.
- employees burn out faster;
§ recommendations.scope.parallelism.not.title
No Parallel Work
No parallel work
§ recommendations.scope.parallelism.not.description
any feature at any given time is done by one person.
@ -136,7 +136,7 @@ one person is deeply involved in a feature.
- more than 80% of commits in a feature are made by one person;
§ recommendations.scope.types.process.title
Poor Processes
Poor processes
§ recommendations.scope.types.process.description
Most features contain one type of task.
@ -165,7 +165,7 @@ It's possible that developers are incorrectly signing commits or the manager is
- style revisions (as a result of focus group feedback);
§ recommendations.scope.plan.title
Develop a Long-Term Plan
Develop a long-term plan
§ recommendations.scope.plan.description
taking architecture into account.
@ -426,7 +426,7 @@ or tasks are poorly split. Need to check. If granularity is the same - take cont
- tasks could have been more complex than they seemed;
- tasks could have had a large volume of work (need to check if the number of changes is also decreasing during this period)
§ recommendations.type.everyHasOne.title: Not Signing Task Types
§ recommendations.type.everyHasOne.title: Not signing task types
§ recommendations.type.everyHasOne.description: Most task types are done by one person.
§ recommendations.type.oneMaintainer.title: Narrow Specialization
§ recommendations.type.oneMaintainer.description
@ -458,7 +458,7 @@ How to fix this:
- change the area of work (tests, documentation, bugs) among employees every sprint;
§ recommendations.type.fewTypes.title
This is a Local Product
This is a local product
§ recommendations.type.fewTypes.description
for a specific customer or problem.
@ -481,7 +481,7 @@ In this case, we see a small number of types, which likely indicates shortcoming
Based on file types, we can assume the type of program (website, server application, DevOps scripts, etc.). For a frontend application, our hypothesis will be more accurate than for DevOps scripts, which might just be a micro-module of initialization.
§ recommendations.type.diff.title
Break Down the Leading Type into Subtypes
Split the popular type into subtypes
§ recommendations.type.diff.description
to detail errors.
@ -496,7 +496,7 @@ Consider several options for subtypes:
- fix (error detected in production);
§ recommendations.type.buddy.title
Accumulate Minor Tasks
Accumulate minor tasks
§ recommendations.type.buddy.description
for new employees.

8
src/ts/translations/ja/pages.ts
View file

@ -107,6 +107,8 @@ export default `
§ page.team.tree.linesAdded: added
§ page.team.tree.linesChanged: changed
§ page.team.tree.linesRemoved: removed
§ page.team.day.commits: Commits
§ page.team.day.activity: Activity
§ page.team.week.title: Weekly statistics
§ page.team.week.date: Date
§ page.team.week.numberTasks: Number of tasks
@ -130,6 +132,12 @@ export default `
§ page.team.pr.all.workDays: Time spent working on a task
§ page.team.pr.all.delayDays: Time of the PR review
§ page.team.pr.middleTimeRelease: The ratio of development time to review time
§ page.team.pr.chart.1day: day
§ page.team.pr.chart.3day: three days
§ page.team.pr.chart.7day: week
§ page.team.pr.chart.14day: two weeks
§ page.team.pr.chart.30day: month
§ page.team.pr.chart.more: more
§ page.team.pr.commits: Commits
§ page.team.pr.date: Merge Date
§ page.team.pr.mergeAuthor: Merged by

16
src/ts/translations/ja/recommendations.ts
View file

@ -25,7 +25,7 @@ working on weekends
- employees burn out faster;
§ recommendations.timestamp.regularWeekendWord.title: Regular Overtime
§ recommendations.timestamp.sometimeWeekendWord.title: Occasional Overtime
§ recommendations.timestamp.sometimeWeekendWord.title: Occasional overtime
§ recommendations.timestamp.weekendWord.description
It might be advisable to change the project manager, analyst, and architect.
@ -52,7 +52,7 @@ But sometimes it happens.
- employees burn out faster;
§ recommendations.scope.parallelism.not.title
No Parallel Work
No parallel work
§ recommendations.scope.parallelism.not.description
any feature at any given time is done by one person.
@ -136,7 +136,7 @@ one person is deeply involved in a feature.
- more than 80% of commits in a feature are made by one person;
§ recommendations.scope.types.process.title
Poor Processes
Poor processes
§ recommendations.scope.types.process.description
Most features contain one type of task.
@ -165,7 +165,7 @@ It's possible that developers are incorrectly signing commits or the manager is
- style revisions (as a result of focus group feedback);
§ recommendations.scope.plan.title
Develop a Long-Term Plan
Develop a long-term plan
§ recommendations.scope.plan.description
taking architecture into account.
@ -426,7 +426,7 @@ or tasks are poorly split. Need to check. If granularity is the same - take cont
- tasks could have been more complex than they seemed;
- tasks could have had a large volume of work (need to check if the number of changes is also decreasing during this period)
§ recommendations.type.everyHasOne.title: Not Signing Task Types
§ recommendations.type.everyHasOne.title: Not signing task types
§ recommendations.type.everyHasOne.description: Most task types are done by one person.
§ recommendations.type.oneMaintainer.title: Narrow Specialization
§ recommendations.type.oneMaintainer.description
@ -458,7 +458,7 @@ How to fix this:
- change the area of work (tests, documentation, bugs) among employees every sprint;
§ recommendations.type.fewTypes.title
This is a Local Product
This is a local product
§ recommendations.type.fewTypes.description
for a specific customer or problem.
@ -481,7 +481,7 @@ In this case, we see a small number of types, which likely indicates shortcoming
Based on file types, we can assume the type of program (website, server application, DevOps scripts, etc.). For a frontend application, our hypothesis will be more accurate than for DevOps scripts, which might just be a micro-module of initialization.
§ recommendations.type.diff.title
Break Down the Leading Type into Subtypes
Split the popular type into subtypes
§ recommendations.type.diff.description
to detail errors.
@ -496,7 +496,7 @@ Consider several options for subtypes:
- fix (error detected in production);
§ recommendations.type.buddy.title
Accumulate Minor Tasks
Accumulate minor tasks
§ recommendations.type.buddy.description
for new employees.

8
src/ts/translations/pt/pages.ts
View file

@ -107,6 +107,8 @@ export default `
§ page.team.tree.linesAdded: added
§ page.team.tree.linesChanged: changed
§ page.team.tree.linesRemoved: removed
§ page.team.day.commits: Commits
§ page.team.day.activity: Activity
§ page.team.week.title: Weekly statistics
§ page.team.week.date: Date
§ page.team.week.numberTasks: Number of tasks
@ -130,6 +132,12 @@ export default `
§ page.team.pr.all.workDays: Time spent working on a task
§ page.team.pr.all.delayDays: Time of the PR review
§ page.team.pr.middleTimeRelease: The ratio of development time to review time
§ page.team.pr.chart.1day: day
§ page.team.pr.chart.3day: three days
§ page.team.pr.chart.7day: week
§ page.team.pr.chart.14day: two weeks
§ page.team.pr.chart.30day: month
§ page.team.pr.chart.more: more
§ page.team.pr.commits: Commits
§ page.team.pr.date: Merge Date
§ page.team.pr.mergeAuthor: Merged by

16
src/ts/translations/pt/recommendations.ts
View file

@ -25,7 +25,7 @@ working on weekends
- employees burn out faster;
§ recommendations.timestamp.regularWeekendWord.title: Regular Overtime
§ recommendations.timestamp.sometimeWeekendWord.title: Occasional Overtime
§ recommendations.timestamp.sometimeWeekendWord.title: Occasional overtime
§ recommendations.timestamp.weekendWord.description
It might be advisable to change the project manager, analyst, and architect.
@ -52,7 +52,7 @@ But sometimes it happens.
- employees burn out faster;
§ recommendations.scope.parallelism.not.title
No Parallel Work
No parallel work
§ recommendations.scope.parallelism.not.description
any feature at any given time is done by one person.
@ -136,7 +136,7 @@ one person is deeply involved in a feature.
- more than 80% of commits in a feature are made by one person;
§ recommendations.scope.types.process.title
Poor Processes
Poor processes
§ recommendations.scope.types.process.description
Most features contain one type of task.
@ -165,7 +165,7 @@ It's possible that developers are incorrectly signing commits or the manager is
- style revisions (as a result of focus group feedback);
§ recommendations.scope.plan.title
Develop a Long-Term Plan
Develop a long-term plan
§ recommendations.scope.plan.description
taking architecture into account.
@ -426,7 +426,7 @@ or tasks are poorly split. Need to check. If granularity is the same - take cont
- tasks could have been more complex than they seemed;
- tasks could have had a large volume of work (need to check if the number of changes is also decreasing during this period)
§ recommendations.type.everyHasOne.title: Not Signing Task Types
§ recommendations.type.everyHasOne.title: Not signing task types
§ recommendations.type.everyHasOne.description: Most task types are done by one person.
§ recommendations.type.oneMaintainer.title: Narrow Specialization
§ recommendations.type.oneMaintainer.description
@ -458,7 +458,7 @@ How to fix this:
- change the area of work (tests, documentation, bugs) among employees every sprint;
§ recommendations.type.fewTypes.title
This is a Local Product
This is a local product
§ recommendations.type.fewTypes.description
for a specific customer or problem.
@ -481,7 +481,7 @@ In this case, we see a small number of types, which likely indicates shortcoming
Based on file types, we can assume the type of program (website, server application, DevOps scripts, etc.). For a frontend application, our hypothesis will be more accurate than for DevOps scripts, which might just be a micro-module of initialization.
§ recommendations.type.diff.title
Break Down the Leading Type into Subtypes
Split the popular type into subtypes
§ recommendations.type.diff.description
to detail errors.
@ -496,7 +496,7 @@ Consider several options for subtypes:
- fix (error detected in production);
§ recommendations.type.buddy.title
Accumulate Minor Tasks
Accumulate minor tasks
§ recommendations.type.buddy.description
for new employees.

8
src/ts/translations/ru/pages.ts
View file

@ -107,6 +107,8 @@ export default `
§ page.team.tree.linesAdded: добавили
§ page.team.tree.linesChanged: изменили
§ page.team.tree.linesRemoved: удалили
§ page.team.day.commits: Коммиты
§ page.team.day.activity: Активность
§ page.team.week.title: Статистика по неделям
§ page.team.week.date: Дата
§ page.team.week.numberTasks: Количество задач
@ -130,6 +132,12 @@ export default `
§ page.team.pr.all.workDays: Время работы над задачей
§ page.team.pr.all.delayDays: Время ревью PR
§ page.team.pr.middleTimeRelease: Отношение времени разработки к времени ревью
§ page.team.pr.chart.1day: день
§ page.team.pr.chart.3day: три дня
§ page.team.pr.chart.7day: неделя
§ page.team.pr.chart.14day: две недели
§ page.team.pr.chart.30day: месяц
§ page.team.pr.chart.more: более
§ page.team.pr.commits: Коммиты
§ page.team.pr.date: Дата влития
§ page.team.pr.mergeAuthor: Влил

8
src/ts/translations/ru/pages_RU.txt
View file

@ -107,6 +107,8 @@ export default `
§ page.team.tree.linesAdded: добавили
§ page.team.tree.linesChanged: изменили
§ page.team.tree.linesRemoved: удалили
§ page.team.day.commits: Commits
§ page.team.day.activity: Activity
§ page.team.week.title: Статистика по неделям
§ page.team.week.date: Дата
§ page.team.week.numberTasks: Количество задач
@ -134,6 +136,12 @@ export default `
§ page.team.pr.mergeAuthor: Влил
§ page.team.pr.author: Сотрудник
§ page.team.pr.middleTimeRelease: Среднее время поставки (дни)
§ page.team.pr.chart.1day: day
§ page.team.pr.chart.3day: three days
§ page.team.pr.chart.7day: week
§ page.team.pr.chart.14day: two weeks
§ page.team.pr.chart.30day: month
§ page.team.pr.chart.more: more
§ page.team.pr.work: разработка
§ page.team.pr.delay: ожидание
§ page.team.pr.days: дней

8
src/ts/translations/zh/pages.ts
View file

@ -103,6 +103,8 @@ export default `
§ page.team.tree.linesAdded: 补充道
§ page.team.tree.linesChanged: changed
§ page.team.tree.linesRemoved: 改变了
§ page.team.day.commits: Commits
§ page.team.day.activity: Activity
§ page.team.week.title: 按周划分的统计数字
§ page.team.week.date: 日期
§ page.team.week.numberTasks: 任务数量
@ -126,6 +128,12 @@ export default `
§ page.team.pr.all.workDays: 任务完成时间
§ page.team.pr.all.delayDays: PR请求的审议时间
§ page.team.pr.middleTimeRelease: 开发时间与审查时间的比率
§ page.team.pr.chart.1day: day
§ page.team.pr.chart.3day: three days
§ page.team.pr.chart.7day: week
§ page.team.pr.chart.14day: two weeks
§ page.team.pr.chart.30day: month
§ page.team.pr.chart.more: more
§ page.team.pr.commits: Commits
§ page.team.pr.date: 注射日期
§ page.team.pr.mergeAuthor: 填写

16
src/ts/translations/zh/recommendations.ts
View file

@ -25,7 +25,7 @@ working on weekends
- employees burn out faster;
§ recommendations.timestamp.regularWeekendWord.title: Regular Overtime
§ recommendations.timestamp.sometimeWeekendWord.title: Occasional Overtime
§ recommendations.timestamp.sometimeWeekendWord.title: Occasional overtime
§ recommendations.timestamp.weekendWord.description
It might be advisable to change the project manager, analyst, and architect.
@ -52,7 +52,7 @@ But sometimes it happens.
- employees burn out faster;
§ recommendations.scope.parallelism.not.title
No Parallel Work
No parallel work
§ recommendations.scope.parallelism.not.description
any feature at any given time is done by one person.
@ -136,7 +136,7 @@ one person is deeply involved in a feature.
- more than 80% of commits in a feature are made by one person;
§ recommendations.scope.types.process.title
Poor Processes
Poor processes
§ recommendations.scope.types.process.description
Most features contain one type of task.
@ -165,7 +165,7 @@ It's possible that developers are incorrectly signing commits or the manager is
- style revisions (as a result of focus group feedback);
§ recommendations.scope.plan.title
Develop a Long-Term Plan
Develop a long-term plan
§ recommendations.scope.plan.description
taking architecture into account.
@ -426,7 +426,7 @@ or tasks are poorly split. Need to check. If granularity is the same - take cont
- tasks could have been more complex than they seemed;
- tasks could have had a large volume of work (need to check if the number of changes is also decreasing during this period)
§ recommendations.type.everyHasOne.title: Not Signing Task Types
§ recommendations.type.everyHasOne.title: Not signing task types
§ recommendations.type.everyHasOne.description: Most task types are done by one person.
§ recommendations.type.oneMaintainer.title: Narrow Specialization
§ recommendations.type.oneMaintainer.description
@ -458,7 +458,7 @@ How to fix this:
- change the area of work (tests, documentation, bugs) among employees every sprint;
§ recommendations.type.fewTypes.title
This is a Local Product
This is a local product
§ recommendations.type.fewTypes.description
for a specific customer or problem.
@ -481,7 +481,7 @@ In this case, we see a small number of types, which likely indicates shortcoming
Based on file types, we can assume the type of program (website, server application, DevOps scripts, etc.). For a frontend application, our hypothesis will be more accurate than for DevOps scripts, which might just be a micro-module of initialization.
§ recommendations.type.diff.title
Break Down the Leading Type into Subtypes
Split the popular type into subtypes
§ recommendations.type.diff.description
to detail errors.
@ -496,7 +496,7 @@ Consider several options for subtypes:
- fix (error detected in production);
§ recommendations.type.buddy.title
Accumulate Minor Tasks
Accumulate minor tasks
§ recommendations.type.buddy.description
for new employees.