youngmon/atlassian-qna huggingface dataset:
Visibility of pending commits/changes
Asked by Andrew Finch:

Is there an easy way to view pending commits which have yet to be built. I'm aware you can view commits for each run in the commits tab. We have moved form TeamCity which showed all pending commits within the main dashboard. This allowed us to easily see which builds were up to date and which had pending changes. I currently have a manually triggered build and have non built changes but have no visibility of this through the UI.


Answers:
author: Daniel Santos
body: Hi [@Andrew Finch](/t5/user/viewprofilepage/user-id/315456)

The easiest way I know will still involve some manual steps. You would need to check the latest build revision and run a diff between that revision and the one in head.   
Bamboo does not have such feature and it seems that not a lot of users request that. I say that because we have an old feature request open for it and it does not have votes:

* [\[BAM-2822\] Show outstanding/unbuilt changes](https://jira.atlassian.com/browse/BAM-2822?jql=project%20%3DBamboo%20%20and%20text~%22unbuilt%20changes%22%20order%20by%20createdDate%20)

Usually, what we do in Bamboo, is configuring a build to be triggered when the changes arrive. Assuming we are ignoring changes in files and folders we don't want to consider (using git ignore and the exclude changesets feature), we would have builds only when necessary. You should not need to manually check when a build can run. Ideally, Bamboo should check the repositories for you and build them when necessary.   
Does it make sense to you?

comments: author: Andrew Finch
body: Thanks Daniel, yes that all makes sense and was effectively what I was doing to compare changes. The majority of our builds use triggers but some are built daily so still an issue.


author: Daniel Santos
body: Hi [@Andrew Finch](/t5/user/viewprofilepage/user-id/315456)

I'm not sure how can I help you further, maybe if you share why you need such a setting. More details would help me to check if we could do something else to help you with this.

Please add your vote and set yourself as a watcher in the feature request I shared. That seems to be the right feature to attack this need.
How to move the data from H2 database to another database ?
Asked by PerennialDevOps:

We are running Bamboo Server 6.1 in production and it is currently running with the embedded H2 database. Seeing the critical condition and the risks of running with the H2 database, we want to move the database to another DBMS, say MSSQL Server.

Can someone direct me on how to proceed with this process ? Also, will it also backup the database if I take the Export and import it in the new Bamboo instance with an external MSSQL database ?


Answers:
author: DPKJ
body: [@PerennialDevOps](/t5/user/viewprofilepage/user-id/2227185)

You are on right path for production setup. H2 is never recommended for that.

On first part of your question,

* The migration is straight forward.
  * Backup old Bamboo instance.
  * Stop old Bamboo instance
  * Install new Bamboo instance,
  * Start new Bamboo instance,
  * In setup wizard (make sure you don't use any of the old directory)
    * Select DB type you want to use
    * Select import option (to import data from old Bamboo instance)
  * Once done, restart and re-index new instance.
* You can follow this guide - <https://confluence.atlassian.com/bamboo/moving-your-bamboo-data-to-a-different-database-289277250.html>

On second part of your question,

* Backup,
  * You can use existing backup strategy
  * But I personally recommend, (this is what I do)
    * Backup SQL DB
    * Backup Home (especially artifacts directory)
  * This link is great for automating your backup - <https://confluence.atlassian.com/bamkb/automating-bamboo-backup-operations-702715390.html>

comments: author: yash_shanker24
body: Thanks [@DPKJ](/t5/user/viewprofilepage/user-id/690016) , can you kindly elaborate more on

* Backup SQL DB
* How to backup current H2 DB ? Or the same is exported alongwith other data when I do Overview \> System \> Export.


author: DPKJ
body: By "Backup SQL DB" I mean using database specific utility to backup your database.

In your case for "MSSQL" Microsoft gives these options - <https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/create-a-full-database-backup-sql-server?view=sql-server-2017>

Your DBA might be aware of this.


author: yash_shanker24
body: [@DPKJ](/t5/user/viewprofilepage/user-id/690016) Got it. Thanks.

Need your comment at last on,

* How to backup current H2 DB ? Or the same is exported alongwith other data when I do Overview \> System \> Export.


author: DPKJ
body: Yes, you are correct DB backup is part of System Export. And hence, you don't need to backup internal DB separately.


author: yash_shanker24
body: Thanks a lot [@DPKJ](/t5/user/viewprofilepage/user-id/690016)


author: DPKJ
body: [@PerennialDevOps](/t5/user/viewprofilepage/user-id/2227185) [@yash_shanker24](/t5/user/viewprofilepage/user-id/2163534)

If this has helped you please mark this as accepted solution and also shade some love by up-vote and like, so that it can help others.
Prevent Elastic Agent from Termination
Asked by Jeremy:

I have an on-prem bamboo server and single elastic bamboo agent in AWS. There have been a few occasions where the communication between the server and agent are interrupted, which results in the elastic agent getting terminated. Deploying a new agent isn't too big of a deal, but there is a bit of configuration that we apply to the instance after it is deployed. Is it possible to increase the timeout between elastic agent and server to prevent the agent from getting terminated? Is there a better way to address the problem? The Automatic instance management feature is currently Disabled.


Answers:
author: jira guy
body: Update your Elastic management to custom. You can then update Idle agent delay time as you wish.

![Screen Shot 2019-10-08 at 1.01.11 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/68784i1679FFBD7C5F1F2E/image-size/large?v=v2&px=999 "Screen Shot 2019-10-08 at 1.01.11 PM.png")

comments: author: Jeremy
body: Thanks for the suggestion, I will give it a try. Is 10mins the default value used when Automatic instance management is Disabled?


author: jira guy
body: 10 is the default


author: Jeremy
body: Thanks for your help, jira guy!

While I'm waiting to see if the change worked, can you help me understand why the instance is being terminated to begin with? The config for Automatic Termination shows EC2 instances will *not* be automatically terminated. Under Automatic elastic instance management, it says EC2 instances must be manually created and terminated as needed. So why does mine disappear?

![eb.png](https://community.atlassian.com/t5/image/serverpage/image-id/68817iCF8EBF74B21562FE/image-size/large?v=v2&px=999 "eb.png")
Shared configuaration with existing project
Asked by Konrad:

Hi,

When creating new project there is an option at the bottom(oddly only for company-managed project types): "Share settings with an existing project". As I am currently on free Jira plan the option is not available; is there an alternative for this?

<br />

Basically, when I create new project, based on previous one (I normally use Deep Clone) I would like the change in project A to propagate to project B. For instance, I would add new field (dropdown menu or descrption etc) or change workflow in A and would like to see that field or workflow change to appear in B. I am dealing with multiple projects that use same template so this would be highly desirable.


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

Not sure that I am following everything you are saying, but let's start with the first thing. You cannot create a new Team-managed project based on another project because by nature and definition, Team-managed projects are totally independent from all other projects.

So, you can only create a Company-managed project based on an existing Company-managed project. Does that answer your first question?

comments: author: Konrad
body: Hi John,

Yes, this answer my question. I switched to company-managed project which made this possible cloning and sincing - I used Elements Copy and Sync at the end. Thank you.


author: John Funk
body: Great! Would you be so kind to click the Answer accepted button to close this for future readers? Thanks!


Tags: cloud

jira-service-management

jira-service-management-cloud

jira-work-management
How to avoid ticket reopening after making a comment on the transitional page?
Asked by Kent YEUNG:

Hello there,

To begin with

- An automation for ticket opening has been set up - if a comment is added on the ticket with the status "completed", the status will be changed back to "work in progress".

- A screen with custom fields and comment field is associated with the transaction from "work in progress" to "completed".

Based on above configurations, below issue happens:

- If an agent add an comment on the screen, the automation rule will be triggered so the ticket status will be changed back to "work in progress", and the agent needs to add the comment at the issue view before changing the status, instead of adding a comment on the screen and have the ticket resolved.

Question:

- Is it possible if our agents can add a comment on the screen and the automated rule is not triggered?

Thanks for the help!


Answers:
author: Stevan Mandi?
body: [@Kent YEUNG](/t5/user/viewprofilepage/user-id/5499509) The reason why that happens is:  
When you have a screen with custom fields on the transition and the agent populates those fields and comment, the first action that is happening is the transition from In progress to Completed and the second action is fields and comment update.  
Hence, the second action (comment added) triggers your automation and the status is reverted to In progress.  
The solution is to modify your automation trigger - ISSUE COMMENTED. Within the trigger there is a dropdown where you can select "Comment is the main action" which will exclude the case when agent adds a comment during transition

comments: author: Kent YEUNG
body: Thanks Stevan. It works :)


Tags: cloud

jira-service-management

jira-service-management-cloud
How to get this Jira View
Asked by Tristan:

Hello,

I am trying to figure out how to get this jira view when creating and customising a project.

This view all the options along the top, rather than the side and a summary board - i cant seem to find this anywhere.

This is in a team-managed jira service, how can i recreate this in a company managed jira service?

![Screenshot 2024-06-06 at 2.19.00?PM.png](/t5/image/serverpage/image-id/328235iCBEA43FB7EE9DA61/image-size/large?v=v2&px=999 "Screenshot 2024-06-06 at 2.19.00?PM.png")


Answers:
author: John Funk
body: Hi Tristan,

This view is currently only available for Business projects.

comments: author: Tristan
body: Hey John,

That makes sense - i can see different types of projects and the one above is a business one. Currently struggling to find any business related projects when creating a new one however, how can we get these to be shown?


author: John Funk
body: Click on Projects, then Create project.

Then click on Work management under the Project templates on the left. Then select the top option - Blank project

Oh, and I highly suggest after you select the Blank project that you click on the Show more link on the bottom left. Then change the Project type to Company-managed.


Tags: cloud

jira-service-management

jira-service-management-cloud
Chhnku
Asked by Chhnku sing:

The Atlassian Community is open to the public

Content posted here can appear in search engines. Please take care not to post sensitive or personally identifiable information or any other internal company information that you would not want to share publicly.chhnku .


Answers:
author: Chhnku sing
body: Chhnku and Sind Bank


Tags: cloud

jira-service-management

jira-service-management-cloud
How do I get all Jira notifications as a reporter? I don't receieve any updates?
Asked by Joseph Marafioti:

As a reporter I should get all updates to that ticket, but I don't receive any even though my notification settings seem are all selected.  

To add and confirm:

- I do receive notifications via email if I have a comment with my name tagged in it

- and there's nothing that appears in my spam folder

![Jotra.png](/t5/image/serverpage/image-id/328221i45035EDD50272C59/image-size/large?v=v2&px=999 "Jotra.png")


Answers:
author: YY Brother
body: Hi [@Joseph Marafioti](/t5/user/viewprofilepage/user-id/5514252)

Welcome to our Community.

It seems you're using JSM. In JSM, the reporter is taken as a customer. There's a customer notification configuration in JSM Project Setting, which will tell you what events/scenarios will notify the customer/reporter.

Hope it helps \& Thanks

YY?


Tags: cloud

jira-service-management

jira-service-management-cloud
Does the JSM project email blocklist prevent user registration from the blocked domains?
Asked by Dwight Holman:

For a JSM project serving external customers, we want a way to block/prevent users from specific domains from registering in the portal. I have read the documentation for JSM email block-lists and this seems to do what we want for email requests:

[Jira Service Management Cloud ... Manage your Blocklist](https://support.atlassian.com/jira-service-management-cloud/docs/manage-your-blocklist/)

But there is **no mention about user registration in the portal**. I have not found documentation or community discussion about this.

Does anyone have experience using this feature? Any tips or advice welcome.

Also, it would be good to be able to view a list of blocked emails. Does the Site Admin \> Audit log show these events?


Answers:
author: Dwight Holman
body: I have now setup and tested this myself. Based on our test the email blocklist only applies to email requests. Customers using blocked email domains can still register and submit requests via the portal, but would not be able to submit an email request.

Not sure what happens if they post updates to an existing request by email.

It looks like we need to implement this kind of logic ourselves using automation...


Tags: cloud

jira-service-management

jira-service-management-cloud
I am trying to update the Introduction text to the portal
Asked by Amanda Gray:

I am in the sandbox for the project doing some testing.

I am the administrator for the project and when I update the Introduction text for the portal it does not update if I go to the Portal URL.

What could I be doing wrong for this to not work?  
![Jira Portal.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/328208iA7D1EB2DA5F066F6/image-size/large?v=v2&px=999 "Jira Portal.PNG")


Answers:
author: Stephen_Lugton
body: [@Amanda Gray](/t5/user/viewprofilepage/user-id/5466766) This is probably a very stupid question, but did you press Save after changing the text?


Tags: cloud

jira-service-management

jira-service-management-cloud
Update JSM tickets based on the progress of linked JIRA ticket progress
Asked by Anil Rao:

We have a JSM instance which accepts forms from user and creates a JSM ticket.

After an approval in JSM ticket, JSM Automation creates tasks in JIRA Software (a different project)for backend operations. JSM links the issue to the JIRA software

Once the backend operations completes in JIRA software Project, Task gets closed. Is there a way for us to automatically close the JSM ticket based on the progress in the JIRA software project ?


Answers:
author: Stephen_Lugton
body: [@Anil Rao](/t5/user/viewprofilepage/user-id/5514202) You can use automation with a 'Linked Issues' Branching, e.g.:  

![For all linked issues.png](https://community.atlassian.com/t5/image/serverpage/image-id/328284i407028C0CF156570/image-size/large?v=v2&px=999 "For all linked issues.png")

You can then add whatever logic you want and transition the JSM ticket,

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


Tags: cloud

jira-service-management

jira-service-management-cloud
How to Link Projects to Display Tickets on the Jira Service Manager Queue?
Asked by Herbert de Oliveira:

Hello everyone,

We are a company working on multiple projects where we use several standard Jira projects and one Jira Service Manager for DevSecOps. Our DevSecOps team handles tasks opened by external teams, and we currently face the need to open two tickets: one in the external teams' original project and another in Jira Service Manager.

I would like to know if anyone has encountered a similar situation and if there is an efficient way to link a project in Jira Service Manager so that tickets from other projects appear directly on the Jira Service Manager Kanban board.


Answers:
author: Hannes Obweger - JXL for Jira
body: Hi [@Herbert de Oliveira](/t5/user/viewprofilepage/user-id/237873)

I'm not sure if a JSM board can be configured to include issues from a different project (it looks like you can't?) - however you should be able to do that in JSW boards. So as a workaround, you could create a board in your JSW project, and try to find a JQL statement that would pull in a.) the issues from your JSM project, and b.) their linked issues from the relevant JSW project(s). (Querying linked issues is quite tricky in itself; the easiest might be to create a specific *issue link type* for this purpose and use it in your filter.)

Alternatively, if you're open to solutions from the Atlassian Marketplace, you'll have some more options. I myself happen to work on an app that might be a good fit for your use case; I'll provide more information below.

Hope this helps,

Best,

Hannes

comments: author: Hannes Obweger - JXL for Jira
body: ... and just to expand on my last point: If you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, [JXL for Jira](https://marketplace.atlassian.com/apps/1224710?hosting=cloud&tab=overview&utm_source=atlassian-community&utm_medium=referral&utm_content=2718944).

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you'd do in e.g. Excel or Google Sheets. It also comes with a range of advanced features, including support for (configurable) *issue hierarchies.* These issue hierarchies can be based on Jira's built-in parent/child relationships (like story/sub-task), and/or based on *issue links* of configurable *issue link types*. This allows creating cross-JSM-JSW views that very much look and feel like (supercharged) queues, like so:

![jsm-jsw-overview.gif](https://community.atlassian.com/t5/image/serverpage/image-id/328342iD4EA45520AD5C5F2/image-size/large?v=v2&px=999 "jsm-jsw-overview.gif")

As every sheet is powered by a JQL statement, you have full control over which issues are pulled in.

Any questions just let me know!


author: Herbert de Oliveira
body: Hi [@Hannes Obweger - JXL for Jira](/t5/user/viewprofilepage/user-id/4289506) thanks for your reply. I will search for a more nativity solution.

thanks.


Tags: cloud

jira

jira-service-management

jira-service-management-cloud
Project A automation rule 'create new issue' to Project B Errors
Asked by Greg Costa:

Project A \& B are both JSM. Project A has the same custom issue type as Project B but different request types.

I have an automation rule that when a customer places a request on the portal on Project A, it creates a new issue in Project B but I have the following issues:  

* Project B issue does not link the ticket to trigger issue despite the Rule builder being the following:
  * Branch: For Current issue
  * Issue Fields Condition: Field equals value
  * Issue fields Condition: Field is not empty
  * Then: Create a new issue in Project B with same issue type
    * Field to Set: Linked Issues Relates to Trigger Issue

There are two branches. one for onboarding and the other for off-boarding. They both are configured the same. The only time this worked is when the action was set to clone issue and not create new issue.

The other problem is that when the issue gets created in Project B, the request type is not automatically added. In Project B, the issue type is associated to the request type (even though the request type does not equally match Project A). Furthermore, I created an automation rule in project B (as a workaround) to 'Edit Request Type - request type used for onboarding/off-boarding' to any new tickets where Issue Fields condition Field matched the onboarding or off-boarding value and it doesnt not work either.   

<br />


Answers:
author: Greg Costa
body: I'm still having this issue. Does anyone have any suggestions?


author: Kseniia Trushnikova
body: Hi [@Greg Costa](/t5/user/viewprofilepage/user-id/5470139),

Are there any errors in the rule log?

You can set a Request type field value with JSON:

```
{
  "fields": {
    "customfield_10010": "5"
  }
}
```

* 'customfield_10010' is the Request type field ID,
* and '5' is a Request type value ID. You can find this ID by hovering over a request type and checking its URL in *Project settings \> Request types*.

In addition, you can link a new issue to a trigger one in the same place in the Create issue action. Here's the example:

![Screenshot 2024-06-06 at 17.36.00.png](https://community.atlassian.com/t5/image/serverpage/image-id/328416i53A9BC943E7FF424/image-size/large?v=v2&px=999 "Screenshot 2024-06-06 at 17.36.00.png")

comments: author: Greg Costa
body: Hi [@Kseniia Trushnikova](/t5/user/viewprofilepage/user-id/4593830) ,

Thank you for your response. I do have the link a new issue to trigger issue within the 'Create Issue' action but I have it set for 'Relates to' instead of 'is cloned by.' See image below. It does not work and no errors are shown.![Screenshot 2024-06-05 at 4.52.49?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/328448i3BA8D8B6FFD9B8D6/image-size/large?v=v2&px=999 "Screenshot 2024-06-05 at 4.52.49?PM.png")  

As for the 'Edit Request Type' action, it should of worked as the logs showed 'No Actions Performed' for other tickets but the one test ticket I created, there was no log entry.


Tags: cloud

jira-cloud

jira-service-management

jira-service-management-cloud
Is it possible to add a customer with a differnt email address domain?
Asked by Scott Dowell:

I want Jora to automatically create a ticket if it receives an email from an alert system from the microsoft.com domain. However, I cannot create them as a customer because the domains do not match our configured domain name.

What can be done so if Jira receives the alert email a ticket/issue/incident is automatically created?


Answers:
author: Nadhila Savira
body: Hi Scott,

This is Nadhila from JSM.

I think it is best that our support team take a look at your site's configurations first before we can make an accurate suggestion. Do you mind asking your site admins to submit a support request to us about this topic?

Here's our support page: <https://support.atlassian.com/contact/>

comments: author: Scott Dowell
body: I have submitted a request


Tags: cloud

jira-service-management

jira-service-management-cloud
Airtrack
Asked by elizandradias:

Boa tarde,

Gostaria de saber onde encontro e como consigo adquirir o produto AirTrack, do Jira Service Management. Estou tentando procurar nos aplicativos do Jira mas n?o consigo encontrar. Teria alguma rela??o com o plano contratado? ![a.png](/t5/image/serverpage/image-id/328184i0AAE81328D11136B/image-size/large?v=v2&px=999 "a.png")


Answers:
author: Jack Brickey
body: hi [@elizandradias](/t5/user/viewprofilepage/user-id/5225166) ,

Acredito que h? um EAP acontecendo agora, mas n?o tenho os detalhes.


Tags: cloud

jira-service-management

jira-service-management-cloud