v0.27: Unnamed jobs in UI

[nitrocode]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

---

Overview of the Issue

I see all jobs exposed: pre, post, plans, etc

None of the non-plans are named appropriately. The normal workflows like plans show up as the PR repo with the PR number. The other jobs show up as a separate row with just the PR number (no PR repo) and links to each job. It's convenient but you have to click on each one to see what it is.

The usernames are all uppercased on the main page (bug?) and normal-cased on the individual job screen as expected.

It would be nice to expose what type of job is getting run: pre, post, etc.

Reproduction Steps

1. Configure a pre workflow hook
2. Configure a post workflow hook
3. Configure a normal workflow
4. Run atlantis plan
5. Go to UI and see jobs

Logs

N/A

Environment details

If not already included, please provide the following:

• Atlantis version: v0.27.0
• Deployment method: eks
• If not running the latest Atlantis version have you tried to reproduce this issue on the latest version: yes

Additional Context

• Related PR feat: Jobs now shown in a table in the main page #3784

[tlorreyte]

Hey 👋🏼 I'm working on it, I don't think I'll solve all the problems mentioned by @nitrocode, but at least display the essential information !

[ShpilerX]

Hello, I'm not sure it falls in the same bucket but FYI. We're seeing Jobs table entries stay even after Gitlab's usual flow (MR created, planned, approved, applied) is done. Is the correct assumption that both Locks and Jobs tables should not display anything as the merge/pull request flow is complete?
Thank you!