JobChain Tasks shows same task more than once

Current Situation

• Assume a job to be re-used in the same job chain.
  • The current job node that makes use of the job is displayed as "running" and shows the corresponding task information.
  • An additional job node that makes use of same job is also displayed as "running" but excludes the task information.
• This is confusing as users expect the "running" status to be related to the job node being executed, not to the job whereever it is used.
• Consider the linked SourceForge post.

Desired Behavior

• A job displayed in a job chain context has a status that depends on the fact that an order is processed for the job chain node that the job is assigned to.
  • If a job is not in period, waiting for a resource (agent, lock, ...) or running and if there is no order for the job chain node or the order is suspended or has a setback then the job should be displayed as pending.
  • Other statuses of a job such as stopped or not initialized are displayed in all job chain nodes.

Maintainer Notes

• The behavior is fine from a technical point of view that indicates the job status. (The same would apply for a job being stopped, as it would be stopped for all job nodes that make use of this job).
• However, users tend not to consider a running task as an indicator of activity but the information about a job "running".
• With a recent bug-fix after 1.11.0-RC6 the task information is displayed just once which is correct. The fact that the "running" status is displayed twice might be surprising, however, this is not an error.