Feat/add relations status size priority task

[adkif]

PR

• Have you followed the contributing guidelines?
• Have you explained what your changes do, and why they add value?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

---

[rahul-rocket]

@adkif Why we added taskPriority additional field while we have priorit column?

Note: @adkif Same for other 2 columns why?

[badalkhatri0924]

We also have to update multiple places in GT if we implement this changes. @adkif @rahul-rocket

CC: @evereq

[adkif]

@rahul-rocket we need to interact directly with objects using the @ManyToOne relationship. the use of text is limited and a greater cost is required

[rahul-rocket]

@adkif @badalkhatri0924 Yes. We can wait for @evereq for feedback on this PR.

[gitguardian]

⚠️ GitGuardian has uncovered 7 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
8046933	Generic High Entropy Secret	07d2a5b	nx.json	View secret
8046933	Generic High Entropy Secret	60fa1f2	nx.json	View secret
8046933	Generic High Entropy Secret	fb00d71	nx.json	View secret
8046933	Generic High Entropy Secret	fb2dc58	nx.json	View secret
8046933	Generic High Entropy Secret	77b50f4	nx.json	View secret
8046933	Generic High Entropy Secret	3d419c7	nx.json	View secret
8046933	Generic High Entropy Secret	8a5a21e	nx.json	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
smee-client	1.2.3	environment	+4	1.79 MB	tcbyrd
probot	12.3.1	environment	+130	27.1 MB	probotbot
@nrwl/nx-cloud	16.3.0	eval, shell	+4	1.92 MB	nrwlowner
lighthouse	6.5.0	eval, network, filesystem, shell, environment	+1	17.4 MB	patrickhulce
@angular/forms	13.2.2	None	+0	2.36 MB	google-wombot
@nestjs/serve-static	3.0.1	filesystem	+6	686 kB	nestjscore
ngx-clipboard	15.1.0	None	+0	122 kB	maxisam
@nrwl/angular	13.10.6	None	+0	1.38 MB	nrwlowner
pino-std-serializers	6.2.2	None	+0	52.2 kB	matteo.collina
ngx-permissions	13.0.1	None	+0	469 kB	alexkhymenko
octokit	2.1.0	None	+60	17.3 MB	octokitbot

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 8a5a21e. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

🟥 Failed Commands
nx serve api -c=production --prod

---

Sent with 💌 from NxCloud.