nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to autoincrement alphanumeric custom field

ariraati

Hi,

I have a read only (single text line) custom field Risk_id

What is the best practise to set Risk_id with alphanumberic value in format of R0001, R0002, R0003 at the time of issue is being created?

About syntax R####
* the value always starts with letter R,
* which is followed by autoincremented 4-digit number ####

If you propose Scriptrunner, please provide sample code.

Accepted answers

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

The best way to do this is not have a separate redundant field for a key.

Why do you think you need a redundant and less useful field than the issue key?

(I know this is a grumpy-looking post, but it really is about looking at your process and data integrity. Unless you have a legacy system that needs those identifiers that your organisation is imposing on your people because they are afraid of change, then using a redundant duplicate key is utterly pointless)

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

The best way to do this is not have a separate redundant field for a key.

Why do you think you need a redundant and less useful field than the issue key?

ariraati

Point understood, but there is a need for another key for ISO27001 quality reporting and tracking. Secondly in the project there are other issues types (e.g. controls, tasks) so it's not ok Risks only have the standard issue like PR-1, PR-4, PR-12 and so forth. Also this is needed, because the project should be copied to another site and the creation of risks should always start from risk key ID R0001.

Nic Brough -Adaptavist-

No there is no need for another key (and it wouldn't be a key anyway, your users would have to waste their time searching for a key because it would never directly identify an issue)

If you want to insist on having different keys for different issue types, then create a new project, with the right key, one for each key you want to use.

This will do two things:

Let you have PR, ID, RI, etc as issue project prefixes
Will create them sequentially, as the Jira issue number part of the key is sequential

ariraati

Thanks @Nic Brough -Adaptavist- , actually with the Customer we ended up to create own projects / issue. These projects shall share their project configuration.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud