Editable Ticket State and Priority (not working) - 6.3.1 Docker

Infos:

  • Used Zammad version: 6.3.1
  • Used Zammad installation type: docker compose (although no elasticsearch and using AWS RDS postgresql as DB)
  • Operating system: Ubuntu 24.04
  • Browser + version: Chrome 128

Expected behavior:

Actual behavior:

Steps to reproduce the behavior:

  • Install using docker compose (see below)
  • Reset db using:
    ** docker exec -it zammad-railsserver-1 /docker-entrypoint.sh rake db:reset DISABLE_DATABASE_ENVIRONMENT_CHECK=1
    ** docker exec -it zammad-railsserver-1 /docker-entrypoint.sh rake db:migrate

In the database editable is set to false - is this correct?

SELECT name, editable, active, to_create, to_migrate, to_config, to_delete from object_manager_attributes WHERE name = 'state_id' or name ='priority_id';
    name     | editable | active | to_create | to_migrate | to_config | to_delete 
-------------+----------+--------+-----------+------------+-----------+-----------
 state_id    | f        | t      | f         | f          | f         | f
 priority_id | f        | t      | f         | f          | f         | f
(2 rows)
docker-compose.yml
version: '3.12'

x-shared:
  zammad-service: &zammad-service
    environment: &zammad-environment
      MEMCACHE_SERVERS: ${MEMCACHE_SERVERS}
      POSTGRESQL_DB: ${POSTGRES_DB}
      POSTGRESQL_HOST: ${POSTGRES_HOST}
      POSTGRESQL_USER: ${POSTGRES_USER}
      POSTGRESQL_PASS: ${POSTGRES_PASS}
      POSTGRESQL_PORT: ${POSTGRES_PORT}
      REDIS_URL: ${REDIS_URL}
      # Allow passing in these variables via .env:
      AUTOWIZARD_JSON:
      AUTOWIZARD_RELATIVE_PATH:
      ELASTICSEARCH_ENABLED: "false"
      ELASTICSEARCH_HOST:
      ELASTICSEARCH_PORT:
      ELASTICSEARCH_SCHEMA:
      ELASTICSEARCH_NAMESPACE:
      ELASTICSEARCH_REINDEX:
      ELASTICSEARCH_SSL_VERIFY:
      NGINX_PORT:
      NGINX_SERVER_NAME:
      NGINX_SERVER_SCHEME:
      POSTGRESQL_DB_CREATE:
      POSTGRESQL_OPTIONS:
      RAILS_TRUSTED_PROXIES:
      ZAMMAD_WEB_CONCURRENCY:
      ZAMMAD_SESSION_JOBS:
      ZAMMAD_PROCESS_SCHEDULED:
      ZAMMAD_PROCESS_DELAYED_JOBS_WORKERS:
    image: ${IMAGE_REPO}:${VERSION}
    restart: ${RESTART}
    volumes:
      - zammad-public:/opt/zammad/public
      - zammad-storage:/opt/zammad/storage
      - zammad-var:/opt/zammad/var
    depends_on:
      - zammad-memcached
      - zammad-redis

services:
  nginx:
    image: nginx:stable-alpine-slim
    volumes:
      - ./nginx/conf.d/default.conf:/etc/nginx/conf.d/default.conf
      - ./nginx/conf.d/ssl.inc:/etc/nginx/conf.d/ssl.inc
      - ./nginx/share/:/usr/share/nginx/html/
      - ./web/media/:/usr/share/nginx/media/
      - zammad-public:/opt/zammad/public:ro
      - ./dhparams.pem:/etc/ssl/certs/dhparams.pem
    ports:
      - "80:80"
      - "443:443"
      - "8080:8080"

  zammad-backup:
    command: ["zammad-backup"]
    depends_on:
      - zammad-railsserver
    entrypoint: /usr/local/bin/backup.sh
    environment:
      <<: *zammad-environment
      BACKUP_TIME: "03:00"
      HOLD_DAYS: "10"
      TZ: Europe/London
    image: postgres:${POSTGRES_VERSION}
    restart: ${RESTART}
    volumes:
      - zammad-backup:/var/tmp/zammad
      - zammad-storage:/opt/zammad/storage:ro
      - zammad-var:/opt/zammad/var:ro
      - ./scripts/backup.sh:/usr/local/bin/backup.sh:ro

  zammad-init:
    <<: *zammad-service
    command: ["zammad-init"]
    restart: on-failure
    user: 0:0
    volumes:
      - zammad-storage:/opt/zammad/storage
      - zammad-var:/opt/zammad/var

  zammad-memcached:
    command: memcached -m 256M
    image: memcached:${MEMCACHE_VERSION}
    restart: ${RESTART}

  zammad-railsserver:
    <<: *zammad-service
    ports:
      - "3000:3000"
    command: ["zammad-railsserver"]

  zammad-redis:
    image: redis:${REDIS_VERSION}
    restart: ${RESTART}
    volumes:
      - redis-data:/data

  zammad-scheduler:
    <<: *zammad-service
    command: ["zammad-scheduler"]

  zammad-websocket:
    <<: *zammad-service
    ports:
      - "6042:6042"
    command: ["zammad-websocket"]

volumes:
  redis-data:
    driver: local
  zammad-backup:
    driver: local
  zammad-public:
    driver: local
  zammad-storage:
    driver: local
  zammad-var:
    driver: local
.env
IMAGE_REPO=ghcr.io/zammad/zammad
MEMCACHE_SERVERS=zammad-memcached:11211
MEMCACHE_VERSION=1.6.29-alpine
POSTGRES_DB=zammad
POSTGRES_USER=zammad
POSTGRES_PASS=<snip>
POSTGRES_HOST=<snip>.rds.amazonaws.com
POSTGRES_PORT=5432
POSTGRES_VERSION=15.3-alpine
REDIS_URL=redis://zammad-redis:6379
REDIS_VERSION=7.4-alpine
RESTART=always
VERSION=6.3

The field itself can not be edited. You can only edit the existing states and priorities. But for this, you need the following permission: admin.ticket_state and admin.ticket_priority

I’ve got all admin permissions but the edit icon isn’t displaying

Could be some browser cache issue or something in this direction.