Problem: Not possible to edit task template after restoring project

[husjon]

Issue

It seem like it is not possible to edit a task template after restoring a project.
The Edit, Copy/Duplicate and Delete buttons are missing.

This also includes new task templates created in the restored project.

Impact

Web-Frontend (what users interact with), Configuration, Semaphore Project

Installation method

Docker

Browser

Firefox, Chrome

Semaphore Version

[docker@nixos:~]$ docker exec -t -i semaphore ash
~ $ semaphore version
v2.9.75
~ $

Ansible Version

No response

Logs & errors

No logs and no errors.

Missing buttons

Dummy project (manually created) for reference

Manual installation - system information

No response

Configuration

{
  "meta": {
    "name": "DiskStation",
    "alert": false,
    "alert_chat": null,
    "max_parallel_tasks": 0
  },
  "templates": [
    {
      "inventory": "NAS",
      "repository": "GitHub",
      "environment": "Empty",
      "name": "Update DiskStation certificate",
      "playbook": "update-diskstation-certificate/playbook.yaml",
      "arguments": "[\"-e\", \"@update-diskstation-certificate/vault.yaml\"]",
      "allow_override_args_in_task": false,
      "description": null,
      "vault_key": "GitHub Vault",
      "type": "",
      "start_version": null,
      "build_template": null,
      "view": null,
      "autorun": false,
      "survey_vars": "null",
      "suppress_success_alerts": false,
      "cron": "0 0 * * 0"
    }
  ],
  "repositories": [
    {
      "name": "GitHub",
      "git_url": "https://github.com/husjon/ansible-semaphore",
      "git_branch": "main",
      "ssh_key": "None"
    }
  ],
  "keys": [
    {
      "name": "None",
      "type": "none"
    },
    {
      "name": "GitHub Vault",
      "type": "login_password"
    }
  ],
  "views": [],
  "inventories": [
    {
      "name": "NAS",
      "inventory": "[nas]\ndiskstation.local",
      "ssh_key": "None",
      "become_key": null,
      "type": "static"
    }
  ],
  "environments": [
    {
      "name": "Empty",
      "password": null,
      "json": "{}",
      "env": null
    }
  ]
}

Additional information

No response

[husjon]

Hmm, I'm not entirely sure how this happened, but I decided to spin up a new container and it is now working as expected. I guess it must have been something weird with my original instance, I've now replaced it.

Closing.

[Yuri-Lima]

@husjon that is actually an issue. I have opened and they are WIP. #1990

[husjon]

@Yuri-Lima ah, nice catch, didn't see that issue when I created mine.
I'll re-open this issue in case the information might help.