youngmon/atlassian-qna huggingface dataset:
Bamboo Clone Throws Plan Exists Error Every time
Asked by Mike Hagesfeld:

When I go through the clone process, it gives me the following error:  

Plan creation failed. Plan XXXXX-YYYYY already exists.

The plan did NOT, in fact, exist, but does now. I can go on to modify it, but this happens EVERY time I clone. Does this happen for anyone else?


Answers:
author: Foong
body: The Plan XXXXX-YYYYY may exist previously and then deleted.

Even though it is not shown in Bamboo, the data still exist in database and it will be cleared in scheduled job.

If the same key still does not work after a day, there might be error during scheduled deletion job. Check **atlassian-bamboo.log** to look for the deletion message to confirm if there is any error, example normal deletion log:

```
2018-09-06 22:55:33,229 INFO [DelayedDeletionThread] [DeletionServiceHelper] Deleting 1 job(s) marked for deletion
2018-09-06 22:55:33,231 INFO [DelayedDeletionThread] [DeletionServiceHelper] Deleting BAM-TEST-JOB1
2018-09-06 22:55:33,376 WARN [DelayedDeletionThread] [S3ArtifactHandler] S3 artifact handling won't work: bucket name is invalid: [null]
2018-09-06 22:55:33,393 INFO [DelayedDeletionThread] [ImmutablePlanCacheServiceImpl] Skipping invalidation, plan is being deleted: BAM-TEST
2018-09-06 22:55:33,394 INFO [scheduler_Worker-3] [DeletionServiceHelper] Completed background deletion in 174.7 ms
2018-09-06 22:55:33,398 INFO [DelayedDeletionThread] [DeletionServiceHelper] Deleting 1 stage(s) marked for deletion
2018-09-06 22:55:33,399 INFO [DelayedDeletionThread] [PlanManagerImpl] Removing 1 stage(s) for plan BAM-TEST
2018-09-06 22:55:33,406 INFO [DelayedDeletionThread] [ImmutablePlanCacheServiceImpl] Skipping invalidation, plan is being deleted: BAM-TEST
2018-09-06 22:55:33,407 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-13] [DeletionServiceHelper] Completed background deletion in 12.94 ms
2018-09-06 22:55:33,413 INFO [DelayedDeletionThread] [DeletionServiceHelper] Deleting 1 TopLevelPlan(s) and/or ChainBranch(es) marked for deletion
2018-09-06 22:55:33,413 INFO [DelayedDeletionThread] [DeletionServiceHelper] Deleting BAM-TEST
2018-09-06 22:55:33,439 INFO [DelayedDeletionThread] [AbstractQuartzTriggerActivator] Scheduler job repository.change.jobs.CHAIN:BAM-TEST:1 not found, not deleted
2018-09-06 22:55:33,468 INFO [DelayedDeletionThread] [ImmutablePlanCacheServiceImpl] Skipping invalidation, plan is being deleted: BAM-TEST
2018-09-06 22:55:33,490 INFO [DelayedDeletionThread] [ImmutablePlanCacheServiceImpl] Invalidating, plan is not in cache or is being loaded: BAM-TEST
2018-09-06 22:55:33,496 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-13] [DeletionServiceHelper] Completed background deletion in 89.54 ms
```


Tags: clone

plan
How to group / organise many deployment environments?
Asked by Daniel Schaller:

Hello,

We have one project that forms the code base for many differently configured instances of the same core product.

Currently we have one deployment project associated with the build plan. However, within this deployment project we manage 20+ environments, 10+ different UAT and 10+ different PROD ones.

It would be nice to be able to visually group (using tabs, e.g. one for UAT, one for PROD) all these different environments.

Or is there any other recommendation out there that could help managing many deployment environments?

We don't want to end up having to create a separate Deployment Project per instance (only to manage two envs within each) either. That's just shifting the problem from n environments in one project to n/2 deployment projects with 2 envs.

Any suggestions welcomed. :-)

Thanks,

Daniel


Answers:
author: Foong
body: Created feature request <https://jira.atlassian.com/browse/BAM-20080>
Can Bamboo be used for release management
Asked by Phillip Matthews:

After Bamboo creates build artifacts (eg: compiler output hex files), is Bamboo used to keep track of releases?


Answers:
author: Gabriel Ribeiro
body: Hi Phillip,

Yes, you can use deployment projects to manage your releases, please take a look at the below documentation for more details:

* [Understanding deployment releases](https://confluence.atlassian.com/bamboo/understanding-deployment-releases-357335182.html)

If you are currently using Jira, you can take advantage of the integration between both applications to have a better control of the release process:

* [Jira - Deploying a release](https://confluence.atlassian.com/jirasoftwarecloud/deploying-a-release-764478183.html)

Please let us know if you have any specific question about this.

thanks.
In Bamboo, how can you determine which git commit generated a given build artifact?
Asked by Phillip Matthews:

I want work backwards from a build artifact (eg: .hex file from compiler output) generated by Bamboo and find the associated .git commit reference used to build this artifact.


Answers:
author: rsperafico
body: Hi [@Phillip Matthews](/t5/user/viewprofilepage/user-id/1844715),

You could iterate over the JOB that published the artifact by consuming a REST API endpoint [http://myhost.com:8085/rest/api/latest/result/{projectKey}-{buildKey}-{buildNumber : (\[0-9\]+)\|(latest)}](https://docs.atlassian.com/atlassian-bamboo/REST/6.6.1/#d2e4319 "http://myhost.com:8085/rest/api/latest/result/{projectKey}-{buildKey}-{buildNumber : ([0-9]+)|(latest)}") \[[GET](https://docs.atlassian.com/atlassian-bamboo/REST/6.6.1/#d2e4329 "GET")\]

As an example, you could run:

```
# replace USERNAME with a user who has VIEW permissions over given plan
# replace http://localhost:8085 with Bamboo's Base URL
# replace PROJ-PLAN-JOB1-1 with buildResultKey. Please refer to Bamboo Variables -
  https://confluence.atlassian.com/x/nwQ_EQ - for more explanation

curl -k -u USERNAME \
     -H 'Content-type: application/json' \
     -H 'Accept: application/json' \
     -X GET http://localhost:8085/rest/api/latest/result/PROJ-PLAN-JOB1-1?expand=vcsRevisions&expand=artifacts
```

As result, you will find the commit information under **vcsRevisions.vcsRevision\[max-result - 1\].vcsRevisionKey**:

```
{
?? ?...
?? ?"vcsRevisions": {
?? ??? ?"size": 1,
?? ??? ?"expand": "vcsRevision",
?? ??? ?"vcsRevision": [
?? ??? ??? ?{
?? ??? ??? ??? ?"repositoryId": 1605634,
?? ??? ??? ??? ?"repositoryName": "My Repository",
?? ??? ??? ??? ?"vcsRevisionKey": "defd4d397004415f683af6f356f59d77c04a9a10"
?? ??? ??? ?}
?? ??? ?],
?? ??? ?"start-index": 0,
?? ??? ?"max-result": 1
?? ?}
?? ?...
}
```

and the artifacts available to build result under **artifact\[1\]** onward.

```
{
    ...
?? ?"artifact": [
?? ??? ?{
?? ??? ??? ?"name": "Build log",
?? ??? ??? ?"link": {
?? ??? ??? ??? ?"href": "http://localhost:8085/download/PROJ-PLAN-JOB1/build_logs/PROJ-PLAN-JOB1-1.log",
?? ??? ??? ??? ?"rel": "self"
?? ??? ??? ?},
?? ??? ??? ?"producerJobKey": "PROJ-PLAN-JOB1-1",
?? ??? ??? ?"shared": false
?? ??? ?},
?? ??? ?{
?? ??? ??? ?"name": "TXT",
?? ??? ??? ?"link": {
?? ??? ??? ??? ?"href": "http://localhost:8085/browse/PROJ-PLAN-1/artifact/shared/TXT/",
?? ??? ??? ??? ?"rel": "self"
?? ??? ??? ?},
?? ??? ??? ?"producerJobKey": "PROJ-PLAN-JOB1-1",
?? ??? ??? ?"shared": true,
?? ??? ??? ?"size": 31,
?? ??? ??? ?"prettySizeDescription": "31 bytes"
?? ??? ?}
?? ?]
    ...
}
```

Please, refer to the following documentation for further information:

* [Bamboo REST API documentation](https://docs.atlassian.com/atlassian-bamboo/REST/6.6.1/ "Bamboo REST API documentation")
* [Bamboo Variables](https://confluence.atlassian.com/x/nwQ_EQ "Bamboo Variables")

Hope the information provided help you somehow.

Kind regards,

Rafael


author: Alexey Chystoprudov
body: There's build variable planRepository.1.revision which contains revision hash. You can use it to generate artifact name or content
How to pause the SLA for the specific time on a specific date
Asked by Chetan Tandon:

Hi,

I would like to understand if there is a way to pause the SLA for a specific time on a specific date. This is mostly required for the next day to a Holiday.

For eg: There is a holiday on Wednesday(SLA is paused) and team joins back on Thursday 9 AM. Is there a way to pause the SLA from 00:00 to 09:00 AM on Thursday(specific date).

Thanks!


Answers:
author: Mikael Sandberg
body: Yes and no. You can update the calendar that the SLA is using to determine when the SLA should be active. You can add holidays to it, but you cannot specify the time for when the holiday should be active, only the date. If you need to specify the time you would have to change the work week settings in the calendar and then change it back after the holiday.


author: Valerie Knapp
body: Hi [@Chetan Tandon](/t5/user/viewprofilepage/user-id/1529013) , thanks for your question.

You should be able to insert holidays in the SLA calendar. Have you already tried this?

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

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

Hope this helps. There is also some documentation here - <https://support.atlassian.com/jira-service-management-cloud/docs/set-up-sla-calendars/>

Cheers


Tags: cloud

jira-service-management

jira-service-management-cloud
[Automation] Update specific fields on a specific ticket
Asked by Ribeiro Perovano_ Patrick _KWLIB_:

I have 2 projects:

* Project 1: Used as change requests for a client and specific configurations.
* Project 2: I use it as a "database" containing customer records and their settings.

I'm trying to create an automation in **Project 1** , where after a ticket status changed to **Done** , an specifics fields in that ticket change the specific fields in **Project 2.**

Automation so far in terms of mapping the fields in order to locate which specific customer it is, etc., has been completed.

My question is: **How do I create an automation (which option to use) to edit fields in a specific ticket in a specific project?**


Answers:
author: Valerie Knapp
body: Hi [@Ribeiro Perovano_ Patrick _KWLIB_](/t5/user/viewprofilepage/user-id/5473233) , welcome to the Atlassian Community and thanks for your question!

You could use a Global Automation for this. I just did an example -

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

Where on the transition of the issue to Done in one project, to branch into another project and add a label to (in this case) all of the issues but you could obviously specify the attributes and which issues to modify.

You could also use a Listener for this in ScriptRunner, if you have the app, but you would also need to know how to script it. Basically Listeners are what they sound like (ha ha) where they are programmed to listen for some event in the system, so something being updated / created / etc and then to do some actions. They are very useful but you need to know a bit of groovy to be able to use them. <https://library.adaptavist.com/> If you are interested, you can check out the library or install and try the app but I think you can achieve something with Automation.

Hope this helps.

Cheers

comments: author: Ribeiro Perovano_ Patrick _KWLIB_
body: Thank you [@Valerie Knapp](/t5/user/viewprofilepage/user-id/4929946)  

That works! :) Cheers


Tags: automation

cloud

jira-service-management

jira-service-management-cloud
I have used Location field (drop down) in one project and created some tickets. Now I want the locat
Asked by shivani_shirguppi:

I have used Location field (drop down) in one project and created some tickets. Now I want the location field as open text field. If I add new location field to screens and remove older field then will it affect the older tickets?


Answers:
author: Harsh
body: Hi [@shivani_shirguppi](/t5/user/viewprofilepage/user-id/5377189)   
Yes, removing the old location field from the screen will affect the old tickets (i.e. you wont be able to see the field and its associated value) in the View screen.

Thank you


Tags: cloud

jira-service-management

jira-service-management-cloud
How can I prevent or auto-remove the reporter from being added as a request participant?
Asked by Nahuel Logghe:

Hello good people!

My problem is the following:

Customers can add new people as request participants to the project by putting their email addresses in the "To" or "Cc" field when they reply to an email notification from a request. We like this feature and want to keep it. However, they often include the reporter's email in their replies too. This leads to the reporter of the issue being added as a request participant, which results in them receiving duplicate notifications whenever a comment is made.

We're looking for a solution where the reporter isn't added as a request participant, or if that's not feasible, a way to automatically remove the reporter from the request participants whenever they're added.

Ideas?


Answers:
author: Dexter de Vera
body: Hi [@Nahuel Logghe](/t5/user/viewprofilepage/user-id/5433828) ,

Customer (if its only a customer without access on your project) can be the reporter, participant, and part of an organization and they will receive only one notification for comments and transitions (even the reporter is included in participant).

It may have a problem in Jira regarding being in two roles at the same time is the Reporter are user of the project (have access) like Assignee and being a participant or part of an organization.

The assignee/Reporter receives system notification because they are licensed agents and included in project, but if they are also added as a participant of if they are part of an organization, they will start receiving both customer notifications and system notification or none, Jira may won't identify what notifications to be send.

Hope this helps.

comments: author: Nahuel Logghe
body: Hi Dexter,

Thank you for your response.

That is not the case with our configuration. The reporter is not a licensed agent, the reporter is the person who created the request at the customer portal or from an email.

The assignee is the person in charge of solving the issue and the reporter is the person who created/reported the issue.

An agent can be the reporter since agents can create requests/issues, but this is not necessarily the case, and more often than not is our customers who create the requests.


Tags: cloud

jira-service-management

jira-service-management-cloud

reporter

request-participant
How to remove closed sprint from current sprint issue?
Asked by leonardo.zaboto:

I would like to remove the closed sprint attached to the sprint field. It is breaking my query when I try to search Sprint is EMPTY. Since the old sprint is there, the EMPTY function is not working as expected.

![22222.JPG](/t5/image/serverpage/image-id/317406i825B5E5D82C74704/image-size/large?v=v2&px=999 "22222.JPG")


Answers:
author: Trudy Claspill
body: Hello [@leonardo.zaboto](/t5/user/viewprofilepage/user-id/5473136)

Welcome to the Atlassian community.

Actually the EMPTY function is working exactly as designed. The Sprint field is not empty; it contains the history of the sprints to which the issue was assigned and never removed. This is working as designed.

If you remove the closed sprint information from the field that will change the sprint reports for those sprints to show the issue as Removed from the sprint. That could impact other sprint metrics.

What are you actually trying to retrieve with your query? If you want to exclude issues that were in sprints that have been closed then you can use

(sprint is empty or sprint not in closedSprints()


Tags: cloud

jira-service-management

jira-service-management-cloud
how to get calculating SLA time remainng in JIRA cloud
Asked by Kishor Mudhili:

hi all,

how do we get calculating SLA time remainng in JIRA cloud. i want to get the reports for all issues with SLA Remain time.


Answers:
author: Vitaly_Berezovsky_SaaSJet
body: Hi [@Kishor Mudhili](/t5/user/viewprofilepage/user-id/5310742)

You can realize this using our add-on [SLA Time and Report for Jira](https://marketplace.atlassian.com/apps/1220741/?utm_source=Atlassian_Community&utm_medium=refferal&utm_campaign=Comment_how-to-get-calculating-SLA-time-remainng-in-JIRA-cloud_20240410).

You need to open the Grid Table to monitor task fulfillment.

![0f8522c6-acfa-4730-a815-7e81a330e367.png](https://community.atlassian.com/t5/image/serverpage/image-id/327953i8FC977972A3E2C53/image-size/large?v=v2&px=999 "0f8522c6-acfa-4730-a815-7e81a330e367.png")

After you can see Enhanced/**Elapsed time** hints (for SLA timers and on column hover) with:

* start and target dates;

* demonstration of data on the percentage of completion SLA to the target date, elapsed and remaining time;

* SLA status;

* type of the Calendar used to calculate time.

![4f923f9c1-f1c4-4de1-9519-89dadaa3c2ff.png](https://community.atlassian.com/t5/image/serverpage/image-id/327746i1006DADA41DFBFFE/image-dimensions/268x136?v=v2 "4f923f9c1-f1c4-4de1-9519-89dadaa3c2ff.png")

You can also export a table report as XLSX or CSV files with elapsed time.

The application has a [30-day trial period](https://marketplace.atlassian.com/apps/1220741/?utm_source=Atlassian_Community&utm_medium=refferal&utm_campaign=Comment_how-to-get-calculating-SLA-time-remainng-in-JIRA-cloud_20240410) and is free for small teams (up to 10 users), so you can check how well it suits you. My team developed it so our support team can help you with the settings


Tags: cloud

jira-service-management

jira-service-management-cloud
Change to allow for all JIRAs to be auto assigned.
Asked by C S Seshagiri:

Hi Team,  

We need to auto assign issues only if the request is from service desk customers.  
Auto assignment should not happen if an internal agent creates it.  

<br />

Thank you.


Answers:
author: Zoey Wang
body: Hi [@C S Seshagiri](/t5/user/viewprofilepage/user-id/5426245)

An automation rule could do the job for you.

Attached is ![Screenshot at Apr 10 20-08-00.png](https://community.atlassian.com/t5/image/serverpage/image-id/317377i638DEF7DE7F8CA56/image-size/large?v=v2&px=999 "Screenshot at Apr 10 20-08-00.png")a basic version for your reference. Of course you would want to adjust to your specific use case.

Also here is a link to Atlassian Template Library - to explore more re [auto-assign issue](https://www.atlassian.com/software/jira/automation-template-library/auto-assign)

comments: author: C S Seshagiri
body: Hi [@Zoey Wang](/t5/user/viewprofilepage/user-id/4512393) ,  

Thanks for sharing rule!

We tried the automation, it is working both for external users and internal agents. So here we would like to have it assigned only for external users. If internal agent raises request from portal it should not assign.  

Thanks!


author: Zoey Wang
body: Hi [@C S Seshagiri](/t5/user/viewprofilepage/user-id/5426245)

Right, that's why the Reporter component should be set up for Customer as you can see in the rule. That ensures only the tickets raised by Customers would be assigned automatically. Given your internal agents are licensed agents only, the agent's ticket won't trigger the rule at all.


author: C S Seshagiri
body: Hi [@Zoey Wang](/t5/user/viewprofilepage/user-id/4512393) ,  

I would like to know what if agent also has customer access?

Thanks!


author: Zoey Wang
body: Hi [@C S Seshagiri](/t5/user/viewprofilepage/user-id/5426245)

Adjust the Report condition - not in "Service Desk Team" for instance, to filter out users being in both Customer and Agent roles at the same time. See if that works for your case.

![Screenshot at Apr 13 11-19-09.png](https://community.atlassian.com/t5/image/serverpage/image-id/318128i7620A8120E89F324/image-size/large?v=v2&px=999 "Screenshot at Apr 13 11-19-09.png")


Tags: cloud

jira-service-desk-cloud

jira-service-management

jira-service-management-cloud
Can you lock an Asset Object Field/Attribute?
Asked by Calvin:

Okay so I have a field say "Serial" and its pre-populated via an automation.

I do not want any users updating this field except via automation (and I guess admin if possible but not required).

Is there anyway I can lock this field/Attribute?

Cheers!


Answers:
author: Zoey Wang
body: Hi [@Calvin](/t5/user/viewprofilepage/user-id/4851947)

I am afraid not. There is no such a granular level of control of object types at this stage. Or if you want, you can raise a [support ticket](https://support.atlassian.com/contact/) for raising a feature request to the team for their further consideration.

comments: author: Calvin
body: Thanks so much Zoey! Sad to hear it isn't available, but great to know at least I'm not feverishly researching for something that isn't available. Cheers!


Tags: cloud

jira-service-management

jira-service-management-cloud
Issue using virtual agent and Atlassian intelligence
Asked by Rik Fisk:

have set everything up as described but the virtual agent which is supposed to search the associated Confluence site is not returning anything. Other answers suggested you needed to Label the confluence pages which we already have ?

The Virtual agent works ok with intents but not Atlassian intelligence.

The slack channel keeps asking you rephrase the question and then leads to creating a ticket

can anyone help ?


Answers:
author: Gary Spross
body: In the "Knowledge Base" section of the project settings, where the Spaces are added, I had to set the "Who can view" option to "All logged-in users". Before I changed that setting, I was getting the same "please rephrase" response every time.


author: Gabriel Jarochevsky
body: I get same results. Virtual Agents seems **not** functional using Slack.


Tags: cloud

jira-service-management

jira-service-management-cloud
How do I set up a mandatory on a dropdowm list, in its 2nd list?
Asked by Joan_Rivero:

*How do I set up a mandatory on a dropdowm list, in its 2nd list?*

++Example:++

In a custom field, being a dropdowm list I have 2 options:

1st dropdowm list (This field is mandatory in the form)  
Option 1 - Mexico  
Option 2 - USA

The 1st dropdown list is related to the 2nd one -

2nd dropdowm List **(I want to make this field required)**   
Mexico: - Mexico DF  
- Guadalajara

USA: - Florida  
- Texas

**++The idea is that both detachable lists are mandatory within the form++**. How can you help me to solve this problem?

Thank you very much for your time


Answers:
author: Mikael Sandberg
body: If you want to do this within a [Form](https://support.atlassian.com/jira-service-management-cloud/docs/use-forms-in-jira-service-management/) this is how I would do it. I would create a conditional section that is based on the value selected in the first dropdown, that way the second dropdown will only be shown if the first one has the value that is selected for the section. Something like this:

![Screenshot 2024-04-09 at 10.16.33?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/317267i2C6DFF5908F59650/image-size/large?v=v2&px=999 "Screenshot 2024-04-09 at 10.16.33?AM.png")

This would mean that the State field will only be visible if USA is selected. You can make the State field required, but it would only be required if the section is visible.


Tags: cloud

jira-service-management

jira-service-management-cloud