Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

creating multiple versions automatically

Sebastian Braun April 13, 2023

Hi all,

I´m searching for a possibility to have multiple versions created automatically in different queues.

To be more precise: I need a new version "2.0" in two queues: ABCD-queue and EFGH-queue.

Once I´ve created the version in ABCD manually, an automation should created a new version with the same name ("2.0") in EFGH.

Is this somehow possible?

I´ve already tried with Jira automation but I don´t know how to get the same name for the second version automatically copied:

2023-04-13 14_47_43-Automation - Jira SANDBOX.png

Thanks in advance.

Best regards

Sebastian

2 answers

2 votes
Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 13, 2023

Hi @Sebastian Braun 

When you talk about „queues“ where versions should be created: do you mean issue queues within 1 project or is each queue a separate project by itself?

In general versions/releases are related to projects not queues. Why would you need 2 different (but obviously same) releases within 1 project? Wouldn‘t be all fixed issues within 1 release?

Furthermore as a version is related to a project as far as I know it‘s not possible to have 2 versions with the same name.

Could you please further specify the use case behind it in more details? I‘m sure there is an appropriate solution for this.

Best

Sebastian Braun April 14, 2023

Hi Stefan,

thanks for your reply. Let me try to explain it in more detail:

We´re using two queues (its called project in Jira) for one customer:

  • ABCD-queue (Jira Service Management for external customer portal usage and support issues)
  • EFGH-queue (Jira Software for internal bug tracking and release management)

Now, we´re planing a new version in EFGH for releasing a software-package, e.g. version "2.0". This version is created manually in the queue (let´s call it "Jira standard way)".

The only reason for us to have version "2.0" also on EFGH is, to communicate it to customer (via content field in portal). As a consequence, the version is called the same, but doesn´t need to be the identical (!) version like in ABCD. There is no planning behind. It´s just for communication reasons.

Therefore I would like to have an automatism, because right now, we have to create two versions "2.0" in both queues (ABCD and EFGH) in parallel.

If you know a better way how to communicate a version from an "internal queue" to the customer automatically, I would be happy to hear it :-)

BR Sebastian

Sebastian Braun September 27, 2023

Hi @Stefan Salzl

could you please check my detailed explanation again?

Thanks in advance.

Best regards

Sebastian

Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 28, 2023

Hi @Sebastian Braun 

so to make that clear we are (in atlassian universe terminology) about 2 different projects

  • 1 project (ABCD) in Jira Service Desk (where customer can raise their incidents)
  • 1 project (EFGH) in Jira Software (where developers working on dev tasks to fix incidents from ABCD

 

my question is:
Is there a link between the tickets from ABCD to EFGH? What is the use case behind it --> when do the issues in ABCD know when or how could you make sure they are really fixed with version x.y.z from project EFGH ?

If there is a linking between issues from the 2 projects and the version is just for communication reasons I guess there will be a solution to just send the version number from EFGH to linked ABCD-issues whenever a version is released (in EFGH).

Best
Stefan

1 vote
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 13, 2023

@Sebastian Braun -

I agreed with @Stefan Salzl statement and asks for further clarification on your question.  In general, version has to be unique where you cannot have duplicate versions created in Jira/JSM env.

One possible idea is for you to consider without knowing more of your ask is create 2 different versions - ABCD2.0 and  EFGH2.0 to somehow makes your queues in sync (meaning those two queues are related to 2.0.  However, it is better just having 1 version of 2.0 and ensure your issues in those two queues to be assigned with the actual "2.0" version, but identify some other meta data fields to separate the issues associated with 2.0 version, so they can be in the appropriate queues.

Hope this helps and looking forward to your clarification on your ask.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Sebastian Braun April 14, 2023

Hi Joseph,

please find my detailed explained above :-)

BR Sebastian

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events