youngmon/atlassian-qna huggingface dataset:
Dependent plans are not always triggered
Asked by Meang Akira Tanaka:

Hi

I am trying working on implementing continuous delivery (CD) in our project and conceptually it should such that every build should cause a new release of the component and subsequently trigger any dependent component to be build with the released components included.

So in order to make this work all dependencies are formed between the bamboo plans through the dependencies tab in the configuration for each component, and in addition to avoid race conditions only one concurrency build is allowed for each component.

Let us say we formed a dependency between project A and project B, such that project A is a parent to project B and it works as expected for most cases.

However I experience whenever project B has started and something triggers project A to be build again (e.g. a push to the repository) and if project A is completed prior to the on going project B has completed no addition job is added to project B i.e. the plan for project B will not build again, and one have to manual trigger B to be build again, which kills my plan of doing CD.

I cannot make up whether this is as intended or not. (Most likely I would say it is intended, as it is also not possible to manually trigger a build on project B once project B has started).

My expectation is that triggering build of dependent plans was guaranteed once it had been formed by bamboo, however that does not seem to be the case.

In case this is intended leads to a conclusion that I may designed my CD wrongly or maybe I have not found the correct way to queue up a builds which also does not allow having concurrent builds.

Anybody who can shed some light one whether it is the former or the latter.

In cases this is intended and I have not designed my CD wrong. Are there anyway to change the behavour adding a plugin extension or something similar?

I would imagine the same holds true if something is pushed into a repository and a build already has started but not completed. But maybe due to a scan later on it will trigger the build again.

Anyway pointers would be appreciated

The bamboo version I am running is 6.3.1 build 60306

Thanks in advance


Answers:
author: Meang Akira Tanaka
body: Seems like this is a known (but) unresolved issue:

<https://stackoverflow.com/questions/34344711/bamboo-wont-trigger-child-plan-if-it-is-already-running>

Please upvote this one: if you want it solved:

<https://jira.atlassian.com/browse/BAM-2820>


Tags: dependency

plan

trigger
How to get the image for Docker Runner?
Asked by wcooley:

Bamboo version 6.4.0 build 60404 - 17 Feb 18

I am having trouble understanding how the Docker Runner is supposed to work: namely, how is it supposed to get the image that it uses?

I can create an earlier stage with a job having a Docker pull task that runs in the agent environment, but I have no guarantee that it will run on the same agent/host.

Likewise, I can create a job in the same stage with the Docker pull task, but that could also run in parallel and/or on another host.

I tried adding a Docker pull task to a job that runs in Docker Runner, thinking that maybe this would be a bit of awkward magic that would run the pull in the agent environment and then run the other tasks in the Docker Runner.

The best I can figure out is that this feature is intended to be used where a local set of images will be downloaded \& maintained by the Bamboo/system admins, outside of Bamboo itself.


Answers:
author: Gabriel Ribeiro
body: Hi Wil,

As stated in the [official documentation](https://confluence.atlassian.com/bamboo/docker-runner-946020207.html), "Docker runner is meant to run builds and deployments in a Docker container to isolate the build process from the environment it runs in." So, basically, Bamboo requires that the image you've set in the task configuration is available locally (agent's environment) or it can be downloaded from the default docker registry.

If you want to ensure that the task will use the latest image, you'll need to push it before the job starts its execution, I would say that the best approach would be to create a "master" plan to build and push the docker image and a "child" or dependent plan to build the project itself.

thanks.


Tags: docker
Pushed code that triggers the build but PlanSpec nothing happens Bamboo Spec Plan
Asked by Tiago Miguel dos Santos Domingues:

Hi,

I?ve setup a project to work with Bambo specs (6.3.1) but when pushing the code the plan does not reflect the changes i did on the code. What i did:

I have followed all the steps in the tutorials, so i double checked and everything seems apparently ok. My integration is between Bamboo and Bitbucket so it should be event smoother

1- Created a linked repository with all the configs as they should be.

2 - I have a branch and a plan that point to this repository.

3 - Pushed code to PlanSpec.java ( e.g. changed the plan description and nothing happens).

Thanks in advance,

Tiago Domingues


Answers:
author: Gabriel Ribeiro
body: Hi Tiago,

I have some questions that may help you troubleshoot this:

* Are you sure that the repository has access to the project you're trying to edit/add plans?
* Are you respecting the default specs project folder structure (repo.git/bamboo-specs/)?
* Are you sure you have Maven 3.2 (or higher) installed on the Bamboo server machine?
* Could you please double check if the "Process Bamboo Specs in Docker" option is enabled in **Cog icon\>Overview\>Security Settings**, if yes, do you have Docker installed on the Bamboo server machine?
* Could you please look for the \[RepositoryStoredSpecsServiceImpl\] class in Bamboo logs (bamboo-home/logs/atlassian-bamboo.log) and see if there are any error messages there?

Let us know if the questions helped you.

thanks

comments: author: Tiago Domingues
body: [@Gabriel Ribeiro](/t5/user/viewprofilepage/user-id/352687) thanks for the great reply. The configs were all good but i was not respecting the default structure for the project. I thought we could integrate it with my existing pom from our main project. Is there a way to override this or we should use separation of concerns ?

Thanks,

Tiago


author: Gabriel Ribeiro
body: Hi Tiago,

I'm afraid that it will not be possible for now. It's a requirement to have the specs project (including the pom.xml file) in the bamboo-specs directory, under the repository root, Bamboo need this "separation of concerns" to distinguish specs project from other projects that you may have in the same repo.

thanks.
Jira Automation: Updating an issue field from selection in Assets
Asked by Trevor de Souza:

Hi,

I am trying to set up an automation so that whenever an issue is created in a project, a custom field linked to Assets is updated in that issue.

I'm not sure what to enter in here.

![Jira Assets PMO.png](https://community.atlassian.com/t5/image/serverpage/image-id/316866iF14C1923B35D6118/image-dimensions/250x285?v=v2 "Jira Assets PMO.png")

In this instance i'm trying to update this field with "Project Management Office" which is an object in one of our Object Schemas


Answers:
author: Zoey Wang
body: Hi [@Trevor de Souza](/t5/user/viewprofilepage/user-id/4929495)

In your Custom Asset field: Program / Portfolio, it expects a ++smart value++ to filter out what value(s) to be allowed to populate when the issue is being edited by automation.

You may also notice a reminder showing in the image

"If the Assets field you're editing can only have one value, and your AQL query returns multiple values, the first value returned by the query will be used for the field."

So please be aware of the custom field settings to align with this bit as well.

comments: author: Trevor de Souza
body: Thanks for the reply [@Zoey Wang](/t5/user/viewprofilepage/user-id/4512393)

So from what I can gather, the AQL syntax I would use would be Name = "Project Management Office"

As the field I am filtering for is called Name and the object is "Project Management Office"

But when I run the Syntax I get an error message:

Error  
An unknown error occurred. Please reload and try again.


author: Zoey Wang
body: Hi [@Trevor de Souza](/t5/user/viewprofilepage/user-id/4929495)

Here is a [post](https://community.atlassian.com/t5/Jira-Service-Management/how-do-i-update-an-Assets-objects-custom-field/qaq-p/2293384) which seems to be able to walk you through with a good example. hope it helps!


author: Trevor de Souza
body: Thanks Zoey.


Tags: assets

cloud

jira-service-management

jira-service-management-cloud
multiple workflows and issue changes
Asked by Yair:

Hi All,

i have a service desk project which I want to use with multiple teams.

When a ticket is created, I want to use an automation to change the issue type which will assign the ticket to the workflow associated with the issue type.

However I am running into some issues. These are the steps I think I need to do:

1. create 2 different issue types

2. create 2 workflows

3. associate each issue type with each workflow

4. use automation to change issue type.

However this doesnt seem to work. The automation fails with this error - "The issue type selected is invalid (issuetype)"

I read 1 blog which said I need to associate both issue types to both workflows. However this doesnt seem to work. Each issue type can only be associated with 1 workflow. Is this true?

If someone has a guide for how to do this I would be very grateful. Again here is what Im trying to accomplish:

Create 1 service desk ticket with multiple answers (done)

Based on the response, use automation to change the ticket type (done but fails)

Have 2 workflows associated with 1 project

Have 2 issues associated with 1 project

Ability to change ticket type and associate with different workflow

Automate this process

Have different views and dashboards for different teams based on the different workflows

Thanks for the help!


Answers:
author: Joseph Chung Yin
body: [@Yair](/t5/user/viewprofilepage/user-id/4634279) -

In JSM, each request type (where users use to file issues to your project) is associated to an issue type used in your project.

Each issue type can only have one WF and while multiple issue types can share a common WF. You cannot have one issue type to be associated with multiple WFs at the same time.

Question for you why you want to change the issue type via automation rule after an issue is created (meaning a request was created)? please advise.

I would recommend you to create different request types to handle what you want to accomplish. This means that you have those request types (based on different issue types) where each issue type can have a different WF to use.

Please provide more information on your reason of changing an issue type after the issue is created, so we can advise you further (i.e. to use automation rule or not).

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

comments: author: Yair
body: [@Joseph Chung Yin](/t5/user/viewprofilepage/user-id/396739) thanks for the answer.

I have created 1 central internal dynamic service desk (using forms) which will compile all internal requests into 1 form. This will eliminate the user creating requests from the wrong team as the form + automation will direct the ticket to the correct team.

This will create 1 ticket in a central service desk. I want each team to be able to use their own workflow. The way I see this happening is to change the ticket type after it has been created using automation.

Thanks for the help!


Tags: cloud

jira-service-management

jira-service-management-cloud
for creating Two Dimensional Filter Statistics gadget, I am not able use the field 'Story Points' Th
Asked by shivani shirguppi:

for creating Two Dimensional Filter Statistics gadget, I am not able use the field 'Story Points' The field is not available in X axis or Y axis dimension. how to make it available.


Answers:
author: John Funk
body: Hi Shivani,

Correct because the Story Points field is open ended and does not have a set list of values. Those types of fields cannot be used with the Two Dimensional gadget (or Issue Statistics gadget).

comments: author: shivani shirguppi
body: Thanks


author: John Funk
body: You are welcome.


Tags: cloud

jira-service-management

jira-service-management-cloud
Is there a REST API to get the customer active/inactive status ?
Asked by Roshinie_105953:

I tried below API.

<https://xxxx.atlassian.net/rest/api/3/user/search?query=abc@company.com>

It will return **"accountType": "customer"** for active customers.

However, nothing returned for inactive customers

So, is there a way to get customer status through any other API?


Answers:
author: Dan Breyen
body: Hi [@Roshinie_105953](/t5/user/viewprofilepage/user-id/4497631) here's what I found for the JSM API calls: [JSM API](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-customer/#api-group-customer)

I may be reading it wrong, but it appears the information is there, but there isn't a specific call to get it.


Tags: cloud

jira-service-management

jira-service-management-cloud
An automation to calculate values off two fields and put the result to 3rd one
Asked by Vera Valshonok:

Hi Community!

How can I make automation to calculate values off two fields and put the result to 3rd one (a field in a ticket)?

I want to start using Impact Start time and Impact End time and to calculate the hours between them in a field called Incident Duration.


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

You can try to do this sample automation process which will trigger when impact start time and end time updated then the action will calculate the diff and display the result in incident duration field:

When: Issue updated - select Impact Start time and Impact End time

Action: edit Issue - select Incident Duration then use this smart value below:

{{issue.Impact Start time.diff(issue.Impact End time).hours}}

Note: Start time and end time should be date time field type.

Hope it helps.

comments: author: Vera Valshonok
body: Thanks! I will try it.


author: YY Brother
body: Hi [@Vera Valshonok](/t5/user/viewprofilepage/user-id/5174542)

Welcome to our Community.

In JSM Cloud, there's already a SLA field to implement your requirement:

* Time to resolution (time duration from creation to resolved excluding non-working hours)

If you want to define a new field, it's difficult to exclude the non-working days/hours from it.

Hope it helps.

Thanks,

YY?

comments: author: Vera Valshonok
body: I need to do this with 3 separate fields, its not related to Ticket statuses time.


Tags: cloud

jira-service-management

jira-service-management-cloud
Scriptrunner (Workflow - Clone issue function) Set request type?!
Asked by Johan Zwart:

Im trying out the "Post-Function Workflow - Clone Issue" function on a JSM Cloud project for a workflow transition.  

First things first, cloning works like a charm!  
Second... Can't figure out how to set a request type on the newly cloned/created issue.

<br />

Im cloning the issue to another project and the new issue requires a request type to be displayed correctly. For now, the new issue has Request type: null...

Is it not possible to achieve this with Scriptrunners "Clone issue" in a Workflow Post-Function?

Edit: Figured out that an API request in the additional code snippet would probably do the trick, but i can't figure out how to fetch the key on the new issue.   
The last line in the log of a cloning is...

```
INFO - Created issue: KEY-123?
```

Is it possible to define "KEY-123" to a variable in the additional code?


Answers:
author: Joseph Chung Yin
body: [@Johan Zwart](/t5/user/viewprofilepage/user-id/5060382) -

As described in ScriptRunner for Jira Cloud - <https://docs.adaptavist.com/sr4jc/latest/features/workflow-extensions/post-functions/built-in-post-functions>

Under the "clone issue" - Step 13 stated "

In the **Additional Code** field modify the `issueInput` structure before it is used as the POST body to `/rest/api/2/issue` to create the issue. For example, add a label, set an assignee, or update the summary of the clone."

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

comments: author: Johan Zwart
body: Viewed the instruction but can't figure out how to modify the request type.  
Can you give me an example?


Tags: clone

cloud

jira-service-management

jira-service-management-cloud

request-type

scriptrunner
How does billing for extension works?
Asked by Jarrod:

Hi Everyone,

The pricing for the Jira products is straight forward. For extensions, I am little puzzled.

For example:

Most Extensions are free for 0-10 users. Once you exceed that am I then getting billed for the Jira Product + the Extensions? The other component I've noticed is that billing is per user and not agent.

My concern is that Jira has a lot of okay features out of the bot but if you really want to use this platform to it's fullest extent, you need to use apps from the marketplace. As you get more users, that will start to add up quickly.

If someone can please break down the billing for marketplace apps. That would be awesome.

Thanks


Answers:
author: Walter Buggenhout
body: Hi [@Jarrod Lovas](/t5/user/viewprofilepage/user-id/5388824) and welcome to the Community!

Billing for extensions (or *apps*, to use the proper term) is a bit complex, but pretty straightforward once you get the basics.

An app follows the number of users for the product family they are for. Suppose you have 25 Confluence users and you add e.g. a diagramming app to Confluence, then you will be charged for the app at 25 users too, as that is the number of paid Confluence users.

I mentioned *product family*, as it is slightly more complex for Jira. If you have paid subscriptions for e.g. Jira Software, Jira Work Management and Jira Service Desk and you install a Jira app, the app will be charged at the highest number of users across those Jira products. This is because Jira is a platform that has a lot of shared cross-product features. Suppose you have 10 JSM agents, 50 Jira Software users and 25 Jira Work Management users and you install a reporting app for Jira, then this will be charged at 50 users - since this is the highest number of users you have for a product of the Jira family.

Hope this helps!

comments: author: Trudy Claspill
body: Adding to this...

The billing is based on "licensed" users. For Jira Service Management that would be Agents. Billing does not count JSM Customers as "users" for billing purposes for the Jira product or the apps.


author: Jarrod
body: Thanks Walter.

I suspected that was the case, I could not find anything to confirm that.


author: Joseph Chung Yin
body: [@Jarrod Lovas](/t5/user/viewprofilepage/user-id/5388824) -

Welcome to the community, as [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225) stated very well on the add-on pricing guideline.

In many cases, if you visit any add-on page in the Marketplace, you can always estimate the cost out for your site via the Pricing tab + in the tab you can see the pricing based on user-tiers "View pricing for different user tiers". You simply need to use the highest number of licenses that you have in your Atlassian product subscriptions (i.e. JSW/JSM/JWM etc..)

Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.


Tags: cloud

jira-service-management

jira-service-management-cloud
How to use the 200SMS on free plan?
Asked by Mariano Edvardsson:

As per JSM pricing scheme, we have 200 free SMS, however, how do I use them to notify agents?

I can't find any place where to setup SMS notifications other than Twilio, but that's another story, right?

![Screenshot 2024-04-06 at 21.39.35.png](/t5/image/serverpage/image-id/316815i276EECCFE9EEE15C/image-size/large?v=v2&px=999 "Screenshot 2024-04-06 at 21.39.35.png")


Answers:
author: Joseph Chung Yin
body: [@Mariano Edvardsson](/t5/user/viewprofilepage/user-id/4480807) -

Take a look at the following reference links -

<https://support.atlassian.com/jira-service-management-cloud/docs/set-up-sms-and-voice-notifications/>

<https://support.atlassian.com/jira-service-management-cloud/docs/alert-notifications/>

Typically, your agents should just access your JSM project to track his/her assigned tasks or access all issues reported by your customers submitted via the queues without the need of using SMS.

Hope this helps

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.


Tags: cloud

jira-service-management

jira-service-management-cloud

mobile

notification
Can a stop recieving automatic emails when i create an issue in my board?
Asked by Furisama:

We use Jira Service Manager and eventhough we need to send emails to our customers when they place requirements, and later an email to rate us, what happens is that **when we create a ticket for our team** , from the "create" button in Jira, **it treats us as customers as well and sends us automatic emails** (and these are other tasks to work on, not customer requests).

I tried to create an automation but there is no rule that "avoids" notifications.

I tried to deactivate notifications from Project settings \> Customer notifications. But there is not specifically one to avoid sending me emails if it is a ticket created by me.

It whould be nice to stop recieving this kind of emails!

Thanks for the help!


Answers:
author: Dexter de Vera
body: [@Furisama](/t5/user/viewprofilepage/user-id/5459872) ,

Welcome to the atlassian community,

If you want to disable your own personal notification, you can go to Yluour profile and settings \> Personal settings - notification then untick the notification you dont want to receive like:

You're watching the issue

You're the reporter

You're the assignee for the issue

Someone mentions you

You make changes to an issue ???---


Tags: cloud

email

jira-service-management

jira-service-management-cloud