youngmon/atlassian-qna huggingface dataset:
Set Release Variables in Bamboo deployment plan
Asked by Marcin Cylke:

I'd like to pass application version to deployment plan for clearer deploy naming.

Is it possible to set a variable in Bamboo build plan and have it available in Release Variables in my Deployment Plan? I've figured I need to have my variable visible in "Metadata" for the build.

I've tried "Inject bamboo variables" step, but this does not result in variables appearing in "Metadata" tab.


Answers:
author: Marcin Gardias
body: If you set the scope of the variables in Inject Task to 'result' they should work in deployments as well (even if they don't show up on Metadata tab, I can't remember if they do for that matter so don't worry about that.

That works since Bamboo 5.8 IIRC.

comments: author: Marcin Cylke
body: I've been down that road before. Today I've tried this again.

The result visible in logs is:

```
Starting task 'inject variables to build process' of type 'com.atlassian.bamboo.plugins.bamboo-variable-inject-plugin:inject'Injected variable bamboo.inject.version=1.25.1-SNAPSHOT in RESULT scope
```

But the variable is not injected into the end results. So the proposed solution does not work. At least for me. Perhaps some other debugging could help?

My Bamboo version is [Atlassian Bamboo](http://www.atlassian.com/software/bamboo/) version 5.9.7 build 5920


author: Jon Stalnaker
body: Were you ever able to get this resolved? I'm trying to do the same thing.

\*\*Disregard, I just had my variable named incorrectly. Result scope worked as expected


author: Andy Kuszyk
body: I'm encountering the same issue in Bamboo 5.11.3.

I've set-up the inject task to set values in the "results" scope, and in the build log I can see that the task has set the correct value to the correct variable. However, in the metadata tab (and in downstream deployment project) the value remains unchanged.

Could this be a bug in the inject task?


author: Phill Fox
body: Have you reviewed this page for how to name your bamboo releases? <https://confluence.atlassian.com/bamboo/naming-versions-for-deployment-releases-361726798.html>

comments: author: Marcin Cylke
body: Yes I have, before asking the question.

There is an example of variable planvar with value 'm6'. But there is no info on how to set the value of 'planvar' variable from some build step. I want that variable to be dynamic (calculated by one of the steps), not statically defined in Plan Configuration.
HIgh JSM License Usage
Asked by gregory_wallace:

The client i have has a very high JSM license usage any wants to know why. They're trying to understand what kind of overlap exists between the licenses to get a better understanding of why the JSM licenses seem so high, why it got so high, and what are good discussion points to start thinking of how to trim it down and keep it under control. Any ideas on how i can put this info together for the client? I'm lost.


Answers:
author: Nic Brough -Adaptavist-
body: I am sorry that the answer you got before was misleading - it was generated by an AI that has no understanding of your question or Atlassian software.

A user counts towards your licence count when their account is given permission to act in a certain role.

In most cases, it's as simple as "can log in and use Jira", for Jira Work Management, and for Jira Software, they also have access to the Software functions.

For Jira service management, the licences are for "Agents" - that is anyone who is an Agent role in at least one JSM project.

The usual reason for licence usage going up when it should not is people leaving their roles, but no-one removes them from their roles in Jira, so their accounts still count against the licence. And, of course, they are usually replaced with someone else, who then consumes another licence.

You need to talk your admins first - are they making leaver's accounts inactive? (Not delete, it is a bad idea, it causes problems. But an inactive account cannot log in, won't be offered as selectable assignees or in other user fields and, most importantly, do not count towards the licence count, even if they are not removed from the roles.

Then talk to your JSM projects owners. Why are they adding more agents to their projects? Are they removing Agents when they no longer need them?

comments: author: gregory_wallace
body: [@Nic Brough -Adaptavist-](/t5/user/viewprofilepage/user-id/781454)

THANK YOU! I may be back in case i have more questions. I hipe that's ok?


Tags: cloud

jira-service-management

jira-service-management-cloud
How to migrate ProForma forms from Jira Data Center non-production instance to a production instance
Asked by Eddy KENTSA:

Our company wants to migrate their projects from a Jira DC non-production instance to the production JIRA DC instance.

The instance has +100 custom Proforma forms that we want to move over. How do we export and import the forms onto the production Jira DC instance without recreating each from manually?

We have tried the plugin Project Configurator to migrate our projects, but it does not include the Proforma Forms.


Answers:
author: Eugenio Onofre
body: Hi [@Eddy KENTSA](/t5/user/viewprofilepage/user-id/5317401)

Welcome to the Atlassian Community.

I would suggest getting in touch with Proforma Support as I could not find any references on their documentation for DC migration.

Please remember to accept this answer in case it helps you resolve your question as it may also help other community members in the future.

Regards,  
Eugenio


Tags: forms

jira-service-management

jira-service-management-server

server
EPIC + atividades serem clonados juntos
Asked by Bianca Branco:

Aqui em nossa equipe, temos ROTEIROS DE EPICS que s?o sempre com etapas iguais. Portanto, quando iniciamos um projeto, queremos copiar estes roteiros inteiros com todos seus itens para este novo projeto.  
Desde j?, agrade?o!


Answers:
author: Trudy Claspill
body: Ol?,

Bem-vindo ? comunidade Atlassiana.

Quando voc? diz que est? iniciando um novo projeto, quer dizer que est? criando um novo projeto Jira? Ou voc? quer clonar o Epic para fazer um novo Epic no Projeto Jira onde existe o Epic original?

Voc? est? tentando clonar apenas um ?pico ou v?rios ?picos?

Com as respostas ?s perguntas acima, poderemos dar-lhe recomenda??es que se aplicam ? sua situa??o espec?fica.

---

Hello,

Welcome to the Atlassian community.

When you say you are starting a new project, do you mean you are create a new Jira Project? Or are you wanting to clone the Epic to make a new Epic in the Jira Project where the original Epic exists?

Are you trying to clone just one Epic, or are you trying to clone multiple Epics?

With answers to the above questions we will be able to give you recommendations that apply to your specific situation.
> EPIC + activities be cloned together
>
> Here on our team, we have EPICS ROUTES that always have the same stages. Therefore, when we start a project, we want to copy these entire scripts with all their items to this new project.  
> Thank you very much in advance!


Tags: cloud

jira-service-management

jira-service-management-cloud
configure open portal
Asked by Pedro Marca Huamancha:

Hello Community,

I want to configure the attached image

![open portal.png](https://community.atlassian.com/t5/image/serverpage/image-id/299097iDB95A886FA9E892D/image-size/large?v=v2&px=999 "open portal.png")

<https://support.atlassian.com/jira-service-management-cloud/docs/set-up-and-manage-portal-access/>

Could you tell me with an image in which part of jira service management I can select the option: **Anyone allowed on the customer access settings** .

![5-01-2024 09-32-03.png](https://community.atlassian.com/t5/image/serverpage/image-id/299098i5DE2114E51BB28D4/image-size/large?v=v2&px=999 "5-01-2024 09-32-03.png")

greetings


Answers:
author: Fazila Ashraf
body: Hi [@Pedro Marca Huamancha](/t5/user/viewprofilepage/user-id/5397238)

Can you confirm that the below settings are already in place?

To do this, the site admin can:

1. From the top right of your screen, select **Settings** () \>**Products**.

2. Under **Jira Service Management****,** select**Customer access**.

3. Select **Allow customers to create accounts**.

4. Select**Customers can access and send requests from the portal without logging in**.

5. Select **Save**.

If yes, please share screenshot of the above list.

Once, that is set correctly then you should be able to find the project level options

comments: author: Pedro Marca Huamancha
body: Hello [@Fazila Ashraf](/t5/user/viewprofilepage/user-id/538419) ,

The previous point is correct, I already have it configured, I share the image.

![5-01-2024 11-53-45.png](https://community.atlassian.com/t5/image/serverpage/image-id/299135iA6D762CF4C2E9780/image-size/large?v=v2&px=999 "5-01-2024 11-53-45.png")

I would like to know where I can configure the next step

![5-01-2024 11-56-28.png](https://community.atlassian.com/t5/image/serverpage/image-id/299136i0B668090F4C90542/image-size/large?v=v2&px=999 "5-01-2024 11-56-28.png")

I would appreciate it if you could share an image showing that option.

greetings


author: Fazila Ashraf
body: Ah sorry, now i get what you mean. The instructions in that link doesnt look valid. I gave a feedback on this article.

The instructions in <https://support.atlassian.com/jira-service-management-cloud/docs/change-project-customer-permissions/> are ok for me. Are they helpful for your use case?


Tags: cloud

jira-service-management

jira-service-management-cloud
Transfer existing Ticket descriptions to new custom field in Jira
Asked by Sem H:

Hello everyone,

I'm currently facing a challenge within Jira Service Management, and I hope you can help me find a solution. My goal is to have a text ready in the custom portal's description (When a ticket will be created). Example: ![opslaan voorbeeld.png](https://community.atlassian.com/t5/image/serverpage/image-id/299088i7CD5AED3BF6D6AB3/image-size/large?v=v2&px=999 "opslaan voorbeeld.png") I tried to achieve this by placing a standard text in the existing description field, but as I couldn't modify this field, I created a new one.

The issue arises when I hide the description field in the request form and add the new field. This works fine in the customer portal but not in the backend. The description field, containing all the information from old tickets, appears at the bottom of the page, thus hidden from customers, while the customer field remains at the top.

What I aim to accomplish is the automatic transfer of information from the old description field to the new customer description field for existing tickets, continuing to use the new field by default. Does anyone have experience with this or any idea about the steps I should follow to make this possible? Any suggestions or assistance would be greatly appreciated.

Thank you!


Answers:
author: John Funk
body: Hi Sem - Welcome to the Atlassian Community!

Create an Automation rule based on a Scheduled trigger. You can use whatever timeframe you want because it will be irrelevant.

For the Scheduled trigger add a JQL for: Description is not empty and "New Field" is empty

where New Field is the exact name of your new custom field (including case).

Then add a new action for Edit Issue

Select the new custom field and then click the 3 dots to the right and select Copy

Click the text and change the "Field to copy value from" to the Description field.

Save and Update/Publish the rule.

Then click the Run rule now button.

Note - you might want to start with a JQL for a single issue in the Scheduled trigger to test it first. Something like Key = ABC-123 where that is one of your issues you want to update.


author: Trudy Claspill
body: Hello [@Sem H](/t5/user/viewprofilepage/user-id/5398980)

Welcome to the Atlassian community.

If you want to copy information from an existing field in an existing issue to a new custom field you have added to the issue, you can do that using an Automation Rule.

<https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/>

Note though that there are limits to how many rule executions you can have in a month (see [this documentation](https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update)). For the Standard plan you are limited to 5000 rule executions per month.

Additionally there is a limit to how many issues can be processed in a single rule execution (see [this documentation](https://support.atlassian.com/cloud-automation/docs/automation-service-limits/)). For how many issues do you need copy the information?


Tags: cloud

jira-service-management

jira-service-management-cloud
Add participant to scrum board
Asked by Sergio M. Gard:

How can I add participant to my scrum board?


Answers:
author: Rebekka Heilmann _viadee_
body: Hi [@Sergio M. Gard](/t5/user/viewprofilepage/user-id/5055632)

You can't. I guess you have a Scrum Board that shows Issues from one project? (That's the default).

You need to add the person to the project by assigning a project role, such as user: [Add users to your project \| Jira Work Management Cloud \| Atlassian Support](https://support.atlassian.com/jira-work-management/docs/add-users-to-your-project/)

comments: author: Rebekka Heilmann _viadee_
body: Some words on the basic concept:

Projects contain issues. One issue is only ever part of one project. Hence the unique ID with the project key.  
Boards are views of issues. Boards can show issues of one or more projects or even a subset of those issues.  
That is all controlled by the board filter.

People have access to Projects (and the issues in it). They can see all boards, but can only view and edit the issues on it that they have access to trough their project roles.


author: Nic Brough -Adaptavist-
body: Thank you for quoting me!


author: Rilwan Ahmed
body: Hi [@Sergio M. Gard](/t5/user/viewprofilepage/user-id/5055632) ,

In a **company managed project** , board is available to all users who can view the **saved filter** on which the board is based.   
Note that they'll also need ***Browse project*** **permission** for the project(s) whose issues are shown on the board.  
To share a board with different people, you'll need to either edit the saved filter OR choose a different filter

In a **team managed project** , you need to add users to project access  
<https://support.atlassian.com/jira-software-cloud/docs/add-people-to-team-managed-projects/>  


Tags: cloud

jira-service-management

jira-service-management-cloud
Setting different SLAs for different ticket types
Asked by Robert Sztrikinacz:

Hey, quite new to Jira, currently setting up a basic IT service desk with three main Work Categories: Incidents, Service Requests and Changes. The idea is that Incidents would have different turnaround times for the same priority as a Service Request or a New Change Request.

I have successfully set up turnaround times to resolution for Incidents using a simple conditional "Work Category" = Incidents using the P1-P5 categories.

However when I try to add a further Goal using "Work Category" = Service Requests it seems to clash with the previous goal and when a service request is raised it does not have a goal time allocated. I'm assuming it's because the Goal has the P1-P5 priorities set and there is a non-removeable priority that states "All Remaining Priorities" that is set to blank.

Is there a way to make this model work using SLAs and priorities? As far as I could tell only the priority can determine the turnaround time in the SLA (Urgency - high/med/low would be good for Service Requests but it does not come up as an option). Would appreciate any help even if it means I'm on a completely wrong track in trying to set this up.

Thanks


Answers:
author: Jack Brickey
body: Hi [@Robert Sztrikinacz](/t5/user/viewprofilepage/user-id/5398871) , it would really help to see a screenshot of what you set up. However, I suspect what you are doing is creating multiple goals where a single combined goal is required. for example the following would represent 4 different Goals

"Work Category" = "Service Requests" AND priority = High

"Work Category" = "Service Requests" AND priority = Med

"Work Category" = Incidents AND priority = High

"Work Category" = Incidents AND priority = Med

comments: author: Robert Sztrikinacz
body: Thanks very much, please see screenshot of current setup for incidents. If I wanted to specify any other Work Category I would need to add a separate goal. However I think the fact that this Goal has the "All remaining priorities" and I cannot remove it clashes with any further Goal.

![Screenshot 2024-01-05 141409.png](https://community.atlassian.com/t5/image/serverpage/image-id/299094iFECD973300DCA9BA/image-size/large?v=v2&px=999 "Screenshot 2024-01-05 141409.png")


Tags: cloud

jira-service-management

jira-service-management-cloud
App Created Custom Fields
Asked by LeRoi Mines:

I've found this [article](https://confluence.atlassian.com/jirakb/how-to-find-which-custom-field-is-provided-by-which-app-or-plugin-in-jira-1131087354.html) for Server Jira, but I cannot find an equivalent for Cloud products.

JSM has a custom field called \[Last Customer Comment Date\] that we did not create. Before we start using this field (or rather populating it through automation), how can we find out which app created this field? At present the field has not been used according to JSM. I would like to not have to create another field to capture the same information.

Many thanks in advace

LeRoi


Answers:
author: Marc - Devoteam
body: Hi [@LeRoi Mines](/t5/user/viewprofilepage/user-id/4201086)

As [@Rebekka Heilmann _viadee_](/t5/user/viewprofilepage/user-id/5182395) mentions, if its from an app its mostly noted in the description of the CF.

You can also check the audit log when the field was created.

The only app I knwo who has this field by default created in Jira is: **Enhancer Plugin for Jira**

Otherwise you can contact Atlassian Support, they can access you instance backend and probably can see when the field was created and by and admin or an app.

comments: author: LeRoi Mines
body: Thanks for your help.

I managed to find the audit log and found the field creation there. It has my name next to it, but I know that I did not create it. I believe it was created by our first JSM project since we have not added any new apps since tstarting to use JSM. So, I feel safe in using this field for it's intended purposes.


author: Rebekka Heilmann _viadee_
body: You could check the Audit Log under Settings \> System

Oftentimes automatically created fields will have a proper description, but I guess you already checked Settings \> Issues \> Custom fields ?


Tags: cloud

jira-service-management

jira-service-management-cloud
Automation rule where Summary starts with different phrases
Asked by Eir?kur Baldur ?orsteinsson:

Hi everybody,

I am looking to build an automation rule which triggers every time an issue is created where the condition is:

Summary starts with "Automatic reply" OR "Error message".

Is it somehow possible to do this in one rule or must I create a rule for each phrase?


Answers:
author: Fazila Ashraf
body: Hi [@Eir?kur Baldur ?orsteinsson](/t5/user/viewprofilepage/user-id/3702649)

AFAIK, as <https://jira.atlassian.com/browse/JRACLOUD-31066> is not there yet, summary starts with a phrase.

But if you are ok for summary contains, then you can use the JQL as condition for issue created event

summary \~ "Automatic reply" OR summary \~ "Error message"

comments: author: Eir?kur Baldur ?orsteinsson
body: Thank you [@Fazila Ashraf](/t5/user/viewprofilepage/user-id/538419)

This is indeed disappointing and I agree with you that this seems like a basic requirement. I am surprised how primitive and limited automation conditions in Jira are in this regard.


author: Jack Brickey
body: Hi [@Eir?kur Baldur ?orsteinsson](/t5/user/viewprofilepage/user-id/3702649) , you could use the issue created trigger and tick the use JQL checkbox and use the below JQL. However, there is not a concept of identifying where a phrase is placed in the summary field, e.g. "starts with". So the rule would trigger anytime an issue is created that includes "Automatic reply" or "Error message" anywhere in Summary.

Summary \~ "Automatic reply" OR Summary \~"Error message"

comments: author: Eir?kur Baldur ?orsteinsson
body: Thank you [@Jack Brickey](/t5/user/viewprofilepage/user-id/853369)

This is indeed disappointing and seems to me like a basic requirement. I am surprised how primitive and limited automation conditions in Jira are in this regard.


Tags: cloud

jira-service-management

jira-service-management-cloud
About profile view error
Asked by ???_??_:

When a customer clicks View Profile to edit their profile on the portal screen, an invalid path error is displayed.

Why is that so?


Answers:
author: Marc - Devoteam
body: Hi [@???_??_](/t5/user/viewprofilepage/user-id/4704901)

It looks like there is something wrong with the user, I can't see this fixed from the GUI.

I would raise this issue related to that user with Atlassian Support, they can check what is happing on the backend in your instance.


Tags: cloud

jira-service-management

jira-service-management-cloud
Any way to create Jira using "Create Linked Issues" functionality without inheriting parent's sprint
Asked by Iris Ionita:

Hey! I wanted to introduce "Create linked issue" as a process in my team in order to expediate the creation of follow-up bugs/improvements to tested tasks Jira completed from previous sprints, but the child issues automatically inherits an old, previously completed sprint.

Is there any way to remove this functionality or are there any plans to amend this in the future?

It pretty much renders what would be a pretty useful feature applicable only when testing tasks and creating follow-up work within that current sprint only.


Answers:
author: Rebekka Heilmann _viadee_
body: Are you sure you are creating a "Linked" Issue and not a Subtask/Child? Assuming you are using cloud, I have tested it in my instance from a task in an active Sprint. It doesn't even "prefill" the Sprint Field when visible and creates the new issue in the Backlog automatically.


author: Marc - Devoteam
body: Hi [@Iris Ionita](/t5/user/viewprofilepage/user-id/5398770)

Welcome to the community.

I second the statement of [@Rebekka Heilmann _viadee_](/t5/user/viewprofilepage/user-id/5182395) and in addition are you not "Cloning" an issue?

The same applies on DC.


Tags: jira-service-management
How to convert incident ticket to problem or change ticket?
Asked by Moon:

Dear community members,

Good day,

Any ideas on how to convert an incident ticket to a problem ticket or a change ticket in JSM cloud?

I cannot find any setting in the incident management module for this. I have explored the FreshWorks product, and I realized that it allows for direct conversion to problem and change tickets

Thanks a lot.

Best regards,

Moon


Answers:
author: Marc - Devoteam
body: Hi [@Moon](/t5/user/viewprofilepage/user-id/5394728)

You need to have request types in problem or change modules of the JSM project.

In best practice, these should have a different issue type as well and their own workflow.

To see the setup I would advise to setup an ootb JSM project, with the ITSM template in your sandbox, as I see you have a premium subscription.

This will show you how Atlassian inteads the usage of the different modules in a JSM project.

comments: author: Moon
body: Hi Marc,

Thanks for your prompt response. Do you have an example link to guide me on how to do it?

Thanks a lot.

Best regards,

Moon


author: Marc - Devoteam
body: Hi [@Moon](/t5/user/viewprofilepage/user-id/5394728)

Create a new JSM project with the ITSM template, this will provide you with an example setup in relation to change, problem, etc...


Tags: cloud

jira-service-management

jira-service-management-cloud