New JobViewer visual element

[jrobinAV]

Objective

This issue aims to create a new visual element named job. The motivation is to have a specific visual element to display information related to a specific Job.

Requirements

The control should have content very similar to the detail panel of a job entry in the job_selector visual element. The same code should be shared by the two visual elements as much as possible.

The job control should accept a Job as the main value.

The job visual element should always display the following fields. A property should control whether the field is displayed or not.

• The job id - always displayed
• The creation date - always displayed
• The status - always displayed
• The submit id - NOT displayed by default
• The task simple label - displayed by default
• The submit_entity label - displayed by default
• The execution duration - displayed by default
• The pending duration - NOT displayed by default
• The blocked duration - NOT displayed by default
• The submission duration (finished_at - creation_date ) - displayed by default
• The stack trace - displayed by default

The job visual element should provide actions to:

• Cancel the job - displayed by default - active only if the status is pending or submitted or blocked
• Delete the job - displayed by default - active only if the job is finished

Expected output

• The implementation of the new control/visual element
• A default style and UX consistent with Taipy styling, in particular, the detail panel of the job_selector
• Unit tests
• Any suggestions to improve the UX, the content of the visual element, or its technical implementation are welcome.

[FredLL-Avaiga]

is this a duplicate of #1251 ?
@jrobinAV

[jrobinAV]

Not really.
I changed the description so it is more clear that this one is about a dedicated job viewer control, while the other is about a detail panel on the job selector.

[Prathamesh010]

Requirement document is not accessible. @jrobinAV

[jrobinAV]

@Prathamesh010 Sorry, the document is private. Instead, I copy pasted the part that concerns the issue in the description directly.

I would be pleased to provide more input if you have any questions.
For technical considerations, @FredLL-Avaiga and @FabienLelaquais are the right persons who can help.

[Nupoor10]

Hi, can you please assign this issue to me, would love to work on this! @jrobinAV

[quest-bot]

New Quest!

A new Quest has been launched in @Avaiga’s repo.
Merge a PR that solves this issue to loot the Quest and earn your reward.

---

Some loot has been stashed in this issue to reward the solver!

🗡 Comment @quest-bot embark to check-in for this Quest and start solving the issue. Other solvers will be notified!

⚔️ When you submit a PR, comment @quest-bot loot #412 to link your PR to this Quest.

Questions? Check out the docs.

[FlorianJacta]

Here you go @Nupoor10 !

[Rishi-0007]

@quest-bot embark

[quest-bot]

@Rishi-0007 has embarked on their Quest. 🗡

• @Rishi-0007 has been on GitHub since 2021.
• They have merged 2 public PRs in that time.
• Their swords are blessed with HTML and TypeScript magic ✨
• They have contributed to this repo before.

This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.

Questions? Check out the docs.

[Rishi-0007]

hey @FlorianJacta, i would like to work on this issue. Please assign this to me. Thank you.

[quest-bot]

🧚 @Nupoor10 has submitted PR #2051 and is claiming the loot.

Keep up the pace, or you'll be left in the shadows.

cc @Rishi-0007

Questions? Check out the docs.