Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 930
    • Issues 930
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Development
  • Core
  • Issues
  • #1046

Closed
Open
Opened Jun 14, 2019 by DaveD@DaveDDeveloper

Proposal to fix longstanding name vs label problems for case roles

Overview

At some point in time the xml case type definition started to use the label for the case role instead of the name. Currently you can't change the relationship type label in the UI without causing problems or in some cases a fatal error.

See

#774 (closed)

#856 (closed)

The first link also includes links to related instances over time.

Proposal

Add a tag to the xml (e.g. <name_for_real_this_time> or <lookupKey> or <optionValueName> etc). When parsing the xml use this tag first, otherwise fall back to using <name> and compare it against label (same as current). This way it won't affect existing installs. For installs using database storage for case type definitions the upgrade script can add this tag to the xml. For sites using files people can add it as needed (possibly the upgrade script can suggest).

Ping @colemanw @eileen @jitendra @andrewhunt @totten Also pinging @bgm since this issue causes language problems too.

Edited Jun 21, 2019 by DaveD
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
5.20.0
Milestone
5.20.0
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#1046