Field Mapping between Jira Discovery and Jira Delivery.

[norman_kreikemeier]

Hi, I currently want to use Jira Discovery for a Customer Support Process, since the Board view of Jira Discovery is perfect for this process.

To properly connect this Discovery Project with a Delivery project, I want to map the custom Jira Disovery Field 'Prio' with the Jira Delivery field 'Priority'.

I tried this via an Automation but without success. Can you help me with that? Is there any chance to implement such a mapping?

It might be important to mention that my idea was to use the Discovery ticket for the implementation and don't link a separate Delivery ticket to it, with the main goal to avoid to many ticket creation in different project and have a single source of truth.

[Tomislav Tobijas _Koios_ · Accepted solution]

Hi @norman_kreikemeier ,

It's probably possible but this would require a little more detail I would say.
For example:

• What type of field is 'Prio' in JPD?
• When looking at 'Priority' are we looking at the system field there?
• If you're not linking JPD and delivery/Jira issue, how do you correlate between the two?

If you can share what you've made so far with automation that would be helpful too.

Cheers,
Tom

[norman_kreikemeier]

Hi Tom,

sure let me try to summarize everything:

Prio in JPD is a Select field.
Priority in the relevant delivery project is a system field.

The current idea is that Customer support creates a JPD issue, which I also show in the Kanban board & backlog of the relevant team by adjusting the board filter.

The automation that I implemented in the JPD project so far is checking for a value change in the field Prio, checking if the Prio is e.g. 'High' to then also edit the field Priority to be set to 'High'.

From the Audit log I get the following error:

Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -
Priority (priority)
No fields or field values to edit for issues (could be due to some field values not existing in a given project):
CS-3

I hope this is giving you a little bit more context?

Thanks for your support!

[Tomislav Tobijas _Koios_]

So, you're just displaying ideas on a Kanban board (as part of one company-managed Jira project). Am I correct? You're not actually creating delivery issues within specific Jira (ex. Software) project?

I've tested the automation when updating 'Prio' (select list) field so that it updates the system Priority field. However, as you can see, when I open this idea on the board in my Jira project, I can see Priority field on the right side under 'Details' panel. If everything I've mentioned earlier is the scenario you currently have, can you check if you've got 'Priority' field visible somewhere on the issue when it's opened from the project board?

[norman_kreikemeier]

Hi Tom,

So, you're just displaying ideas on a Kanban board (as part of one company-managed Jira project). Am I correct?

Correct.

You're not actually creating delivery issues within specific Jira (ex. Software) project?

Correct.

I can confirm, that I can see the 'Priority' field in the issue when I open it on the delivery board.

The main issue is, that the Automation does not want to work. It currently looks like this and is created in the Discovery project, where it is triggered, but running into the above mentioned error:

What is the difference in the Automation setting compared to yours?

[Tomislav Tobijas _Koios_]

Hmm, there shouldn't be any difference (I'm just using IF/ELSE block but that's it). Also, you can ignore these first two actions after the trigger as I was just testing something out. Can you share how you've configured Edit issue action?

*one additional question - can you check/confirm if you have any additional custom fields on instance that are called "Priority"?

Few questions:

• Could you maybe also share the rule details?
• Is the scope set to the JPD project or is it global?
• Also, who's set as rule actor?

I've been using JPD and automation for a while, but this is just a quite specific use case (at least I've never encountered it) so it might take some time to get this figured out 😅

[norman_kreikemeier]

Moin Tom,

here you go.

1. The details of the Edit issue fields action:
   1. 
   2. I haven't done any changes to the 'more options' part so far.
2. I haven't see any additional Priority field that was added to the project. You can also see it in this screenshot:
   1. 
3. And here you can see a screenshot from the rule details.
   1. It's set as it was initially: Single Project with the JPD, Rule Actor is 'Automation for Jira'. (Not sure if important, but I had to leave the project automations and go the to global automations to see details as scope.
   2. 

I hope this information is helpful to find the issue on my side.

[Tomislav Tobijas _Koios_]

Morning @norman_kreikemeier ,

I'm almost out of ideas, but can you check/try the following:

• Check if you can manually change Priority on the issue view on the board.
  Additionally, you may want to check if you can manually change the field value if you go to Filters > View all issues > *add Priority field as a column > *try to change the value from there
• If you can do this manually, replace the rule actor and set yourself. 
• Check the Priority scheme (Settings > Issues > Priority schemes) and check which one is connected with your JPD project.
• Try to remove it and then add the same action to set the Priority value.
• Try adding another Edit issue action and updating some other fields - try updating one JPD field and then one Jira global field (which is visible when you open the issue on the board); with Automation user as actor.

I didn't manage to find the screen from which fields visible on the 'board view' are pulled. 🤔

If nothing, you can also reach out to Atlassian Support with this question and give them permission to access your site. It would probably be much easier to debug it. You can also reference this discussion in your ticket.

Cheers,
Tom

[norman_kreikemeier]

Thanks for all the ideas and input!

Let me shortly run through the list:

1. Check if you can manually change Priority on the issue view on the board.Additionally, you may want to check if you can manually change the field value if you go to Filters > View all issues > *add Priority field as a column > *try to change the value from there

   1. The Priority field is just shown in the Kanban project. There I can change it 👍 (I can not see the Prio field there, which I can see on the JPD board.)
2. If you can do this manually, replace the rule actor and set yourself.
   1. This was solving the problem ✅
   2. The weird thing is, that the permission scheme seems to be correctly configured 🤔
      1. 

Do you have any last idea why the Automation user can not execute the Priority change?

Thanks a lot Tom!

[Bill Sheboy]

Hi @norman_kreikemeier -- Welcome to the Atlassian Community!

Although I understand "what" you are trying to accomplish, it does seem to stray into the area of unsupported / undefined behavior for Jira products. 

I hypothesize the Atlassian intent is for JPD to host portfolio-scope Ideas and their implementation (including use of Kanban boards, reports, etc.) is provided with issues defined in other project types, linked to the Ideas.

Jira Product Discovery (JPD) projects seem to be built upon Team-managed projects (TMP), although many of the features appear to be implemented by different code (not supported by the public REST API) and there is a different permissions model than other products.

• Automation rules use the REST API to perform actions, often with the actor of Automation for Jira, and so some Idea updates may not be supported in rules yet
• The Automation for Jira user has more permissions than a standard user.  However, with JPD's permission model, most things related to Idea creation / update require a "Creator" permission.  This is why you observed the difference: your user likely has "Creator" permission for JPD.  There are several community posts noting this limitation, including...
• There seems to be something different for rules defined / executed within a JPD project and rules defined in a Jira Software (or at the global / multiple-project scope).  That is, the Automation for Jira user seems to have additional permissions when the rule is defined in JPD.  This "one-off" for rule behavior is likely a response to the challenges caused by the JPD licensing model.

Kind regards,
Bill

[Tomislav Tobijas _Koios_]

Hi @Bill Sheboy ,

I agree that this is an 'out-of-scope' use case if we could say so. However, my question here would be why, for example, I managed to get it to 'work'? Specifically, this part about Automation user being able to update the 'Priority' field value. So, on my (demo/test) instance that worked just fine, while @norman_kreikemeier reported that he could not get the Automation user to update the field. Also, my JPD project is set to Private access if that could be relevant.

Regarding this part, Norman asked:

Do you have any last idea why the Automation user can not execute the Priority change?

Could it be that there are some (background) differences when it comes to cloud sites so that's why they cannot get it to work?
Honestly, I'm out of ideas on what could be configured further so they can test it out.

Cheers,
Tom

[Bill Sheboy]

Hi Tom,

If you have both JPD "Creator" permission and at least Jira Site Admin permission, I suspect many things are possible-ish in rules that other users may not observe. 

I suspect Atlassian Support would need to look at their internal logging to know why this scenario is / is not working for Norman's rules.  Plus, Atlassian certainly has inside-knowledge of what is possible with app end-users, permissions versus any JPD feature code using other access methods.

Thanks, and kind regards,
Bill