Configure project key sequence

[Spasimira Genova]

Hi community!

Our incident management team would like to start documenting soft actions into their project and we are looking into the best solution for their needs.

First suggestion which solves their problem is to introduce a sub-task issue type into their project, however, they want the sequence of the issue keys to follow the order of creation of the parent issue, which unfortunately is not possible if they create subtasks.

For example, if they create parent SO-123, and create multiple sub-tasks under it, they want the next parent created to be SO-124. Is there a workaround for this?

Another option is to add a new issue type to the project but again, ideally, each issue type would have a key that follows the sequence of creation for that issue type only. They need the order of the issue keys for reporting purposes.

Is there a workaround to achieve this?

[Jack Brickey · Accepted solution]

Unfortunately, you cannot control the sequencing order of tasks the way you desire. One possible consideration, though, assuming that simple linking is not sufficient, is to create a custom number field and use automation to fill in the information that you desire. You have to play around with exactly the right approach that meets the teams need to here.