# Feature COMMS-662 - Better UX for setting project identifiers during creation or update

Project: Stream Communicator
Status: closed
URL: https://community.openproject.org/work_packages/COMMS-662

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 17.4.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Integrations / Jira, Modules and project features / Project creation |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/NHUuezDJWmeG8LsH2OgVMh/Project-identifiers?node-id=316-2176&t=DmUtIo2hLBg4uFpe-0 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** a user on a instance that uses (soon project-based) work package identifiers  
**I want to** get a suggestion for a short identifier based on the name when I create a new project  
**so that** the project gets an identifier which is suitable for project-based work package identifiers right from the beginning

**Acceptance criteria**

*   On the "new project" view there is a new field "Identifier" between "Name" and "Description" (see Mockups)
    
*   When the user types in a name, a suggestion for the identifier is added to the "Identifier" field
    
    *   The identifier is updated in place if the name changes
        
    *   Depending on which work package identifiers the instance is using (project-based vs. numerical), the suggestion is either a short uppercase identifier or a long lowercase identifier
        
*   The user can edit the "Identifier" field, if he or she does not like the suggestion
    
    *   Then the field is validated against the rules
        
*   When the user "Continues" to the next page and goes "Back" again to change the name, the identifier is updated again
    

**Technical notes**

*   There already is code for suggesting short identifiers, this should be reused
    
*   There already is code for suggesting long identifiers, this should be reused if possible (see `acts_as_url :name` in `project.rb`)
    

**Permissions and visibility considerations**

*   No changes
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._

**Release communication**

*   We simplified the UX for setting and updating the project identifier.