Datasets:

---

youngmon

/

atlassian-qna

like 2

[ { "author": "Steffen Opel _Utoolity_", "body": "Hi [@robbie_kohler](/t5/user/viewprofilepage/user-id/1607182), and welcome to the Atlassian Community!\n\nThe sibling GitHub app documents a fairly advanced GitHub [environment name mapping](https://developer.atlassian.com/cloud/compass/integrations/integrate-Compass-with-GitHub/#github-environment-name-mapping) to infer the environment type.\n\n* NB: The Compass UI annoyingly still only supports staging and production environment types, even though the API supports more, see my answer to [Cannot see development environment for Compass component](https://community.atlassian.com/t5/Compass-questions/Re-Cannot-see-development-environment-for-Compass-component/qaq-p/2405027/comment-id/277#M277)).\n\nThis kind of documentation is missing for the GitLab app, but without being an active GitLab user myself, there seems to be the concept of [environment tiers](https://developer.atlassian.com/cloud/compass/integrations/integrate-Compass-with-GitHub/#github-environment-name-mapping), which are indeed used in the GitLab app's source code, see e.g. [mapEnvTierToCompassDeploymentEnv](https://github.com/atlassian-labs/gitlab-for-compass/blob/e1b780784a4ebf1b027d1e963e3b4a02b256b1c7/src/services/deployment.ts#L33):\n\n```\nexport const mapEnvTierToCompassDeploymentEnv = (env: EnvironmentTier): CompassDeploymentEventEnvironmentCategory => {\n\n switch (env) {\n case EnvironmentTier.PRODUCTION:\n return CompassDeploymentEventEnvironmentCategory.Production;\n\n case EnvironmentTier.STAGING:\n return CompassDeploymentEventEnvironmentCategory.Staging;\n\n case EnvironmentTier.TESTING:\n return CompassDeploymentEventEnvironmentCategory.Testing;\n\n case EnvironmentTier.DEVELOPMENT:\n return CompassDeploymentEventEnvironmentCategory.Development;\n\n case EnvironmentTier.OTHER:\n\n default:\n return CompassDeploymentEventEnvironmentCategory.Unmapped;\n\n }\n};\n```\n\nAccordingly, you can probably make the events show up when you ensure that your GitLab environments have either the staging or production tier.\n\nGood luck!\n", "comments": null } ]

[ { "author": "Alie Sesay", "body": "Hey Paul, and welcome to the community!\n\nSince Basic users are primarily catalog consumers with limited permissions, they don't have access to view any metrics, whether **predefined/built-in** or **custom** metrics.\n\n![Screenshot 2024-08-13 at 11.16.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/341470i5A339CC4EDA178BC/image-size/large?v=v2&px=999 \"Screenshot 2024-08-13 at 11.16.jpg\")\n\n\\* Reference: [Compass user roles](https://developer.atlassian.com/cloud/compass/getting-started/understand-user-roles-in-Compass/)\n\nI hope this clarifies things! Please feel free to reach out if you need any further assistance.\n\n<br />\n\nBest regards, \nAlie\n", "comments": null } ]

[ { "author": "Michelle Carr", "body": "Same Issue here\n", "comments": null }, { "author": "kiran_kantrathi", "body": "Hello @Compass, \n\nCould you please look into it question and reply back? We have recently subscribed to Compass components and now I have a road block here. I would be great if I can have some quick reply here.\n", "comments": null } ]

[ { "author": "Tushar Gohel", "body": "Hello [@visby8em](/t5/user/viewprofilepage/user-id/3565089)\n\nThere no online training available but there are learning resources that you can use.\n\n<https://www.atlassian.com/software/compass/resources>\n\n<https://ace.atlassian.com/events/details/atlassian-live-learning-presents-get-started-with-compass-march-2024-cohort/>\n\nThanks,\n\nTushar\n", "comments": null } ]

[ { "author": "Katie Silver", "body": "Hi [@kiran_kantrathi](/t5/user/viewprofilepage/user-id/5520043) , there isn't a way to do this today I'm afraid. However I am collecting feedback like this so we can prioritize it in the future, and I'll add you to the list. I'm hoping we can do it soon, but at present I can't commit to a timeline.\n", "comments": [ { "author": "Quan Vo", "body": "Hi [@Katie Silver](/t5/user/viewprofilepage/user-id/641274) , this type of request was raised from 2019 like this one <https://jira.atlassian.com/browse/JSWCLOUD-17601>\n\nWhy does it take you and the Atlassian team so long to prioritize the needs of many people and companies?\n" }, { "author": "Joao Santos", "body": "hello [@Katie Silver](/t5/user/viewprofilepage/user-id/641274) any update on this? it is really important if you want us to use compass,..\n" } ] } ]

[ { "author": "Dave Rosenlund _Trundl_", "body": "Hi, [@Matt Richards](/t5/user/viewprofilepage/user-id/5202592). As far as I know, the answer is no. Everything is spelled out in [this document](https://developer.atlassian.com/cloud/compass/components/assign-and-update-a-components-owner/).\n\nSorry to be the bearer of bad news,\n\n-dave\n", "comments": [ { "author": "Matt Richards", "body": "Thanks for the clarification. Bummer!\n" } ] }, { "author": "Jonathan Appel", "body": "[@Matt Richards](/t5/user/viewprofilepage/user-id/5202592) not an ideal workaround but you could create teams of 1. ?\n", "comments": [ { "author": "Matt Richards", "body": "Yeah, that's what we are going to do, and we'll use the name of the individual for the team name. Ridiculous that we have to go about it this way, but typical of Atlassian.\n" } ] } ]

[ { "author": "Josh_Unito", "body": "Hi [@Suzanne Cooley](/t5/user/viewprofilepage/user-id/4931709), you're right - Compass doesn't support self-hosted repos in Jira. So you're not doing anything wrong! I found this in [an Atlassian developper doc](https://developer.atlassian.com/cloud/compass/components/import-components-from-GitLab/):\n> *only GitLab.com SaaS/cloud hosted instances are supported, we do not currently support self-managed GitLab instances*\n\nIf you're looking for an alternative solution for connecting a self-hosted GitLab to Jira though, I can recommend [Unito's integration for Jira GitLab](https://bit.ly/ATL-KB-JiraGitLab). Here's a [guide to setting up the self-hosted server](https://bit.ly/ATL-GitLabOnPrem) to sync GitLab with Unito.\n\nIf this was a helpful answer, please don't forget to accept it as the solution!\n\nThanks,\n\nJosh\n", "comments": [ { "author": "Josh_Unito", "body": "[@john smith](/t5/user/viewprofilepage/user-id/5501932) I just wrote this guide on [how to import issues from Jira to GitLab](https://bit.ly/ATL-GitLab-Jira-Guide) with Unito's 2-way integration.\n\nIt should be pretty clear, but let me know if it's not!\n\n1. [Sign up for Unito](https://bit.ly/UnitoSignUp) (comes with a free trial!)\n2. Create a flow (a no-code integration)\n 1. Connect your GitLab and Jira accounts\n 2. Set a flow direction (Unito can automatically create issues in GitLab based on your issues in Jira and vice versa)\n 3. Apply rules (point and click interface to set conditions: e.g., only sync issues from Jira to GitLab with the XYZ label or issue status)\n 4. Link fields (choose exactly which fields you need to sync between Jira and GitLab)\n 5. Launch!\n\nFeel free to reach out with any questions\n" } ] } ]

[ { "author": "Enrique Serrano Valle", "body": "Hi, [@Patrick Smyrl](/t5/user/viewprofilepage/user-id/5504505) !\n\nCurrently the Compass GraphQL and the Rest APIs don't allow to directly push PR events - the documentation should be updated shortly to reflect this. Is this when you were receiving 400s?\n\nOtherwise, installing the GitHub app in Compass [following these steps](https://developer.atlassian.com/cloud/compass/integrations/integrate-Compass-with-GitHub/), and adding a repository link to your Compass component should be updating PR metrics. PR events don't currently show in the activity feed but you would know that the setup has worked because you'd see the data connection next to the repository link added to your sidebar, the \"open pull requests\" metric populating and a link to the source repository just at the bottom of that metric.\n\n![Screenshot 2024-05-24 at 3.09.52?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/325892i876C3BEE09AFB826/image-size/large?v=v2&px=999 \"Screenshot 2024-05-24 at 3.09.52?PM.png\")![Screenshot 2024-05-24 at 3.10.03?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/325891iBA1FFEB0BA811924/image-size/large?v=v2&px=999 \"Screenshot 2024-05-24 at 3.10.03?PM.png\")\n\nLet me know whether that worked! If for any reason that still didn't solve it, please let us know - providing the site that is used for these tests could also help us narrow down other factors.\n", "comments": [ { "author": "Patrick Smyrl", "body": "I am getting the deployment frequency, so I know there is connectivity between the repo and Compass, but the Open PR's still are not populating. Any thoughts?\n" }, { "author": "Enrique Serrano Valle", "body": "You can verify that you're using the latest version of the Compass GitHub app in your Compass instance as \\`<https://yoursite/compass/marketplace/discover/app/compass.github>\\` and update it if necessary.\n\nOtherwise it may be related to something specific to your configuration. If the issue persists, either sharing your site name here, or opening a support ticket with Atlassian and providing more installation information there may help triage this situation.\n" } ] }, { "author": "xhammer", "body": "I have a similar issue which is that I can see an open pull request on the components and the components are assigned to my teams. But in my team on the pull requests tab I'm showing 0 pull requests.\n", "comments": [ { "author": "Enrique Serrano Valle", "body": "Hi, [@xhammer](/t5/user/viewprofilepage/user-id/5478352) ! The Open PR metric count that you see in the component is populated based on the connection to the repository associated with that component (the repository link that you have added to the right sidebar) so that means that the data connection is successful.\n\nThe pull requests tab under Teams would aggregate PR information at the Team level. The first thing I'd confirm is whether the Team assigned to the Component where you're seeing the PR count (in the top-right sidebar) is exactly the same Team that you're checking the pull requests information for, in the Teams \\> (Your team) \\> Pull requests section.\n" } ] } ]

[ { "author": "Jonathan Appel", "body": "Sounds like you have a monorepo. A few others have asked similar questions but no clear direction yet.\n\n1. <https://community.atlassian.com/t5/Compass-questions/Support-for-monorepos/qaq-p/2350062>\n2. <https://community.atlassian.com/t5/Compass-questions/How-can-I-disable-derived-metrics/qaq-p/2645416>\n", "comments": [ { "author": "Jordan Stone", "body": "Thanks Jonathan; seems like Compass just doesn't support this use case.\n" } ] } ]

[ { "author": "Katie Silver", "body": "Hey [@Ken Young](/t5/user/viewprofilepage/user-id/4596309) , we're working out the details of this now. When we are closer to releasing the on call and alerting functionality in Compass, I'll make sure to update here.\n", "comments": [ { "author": "Ken Young", "body": "Thanks [@Katie Silver](/t5/user/viewprofilepage/user-id/641274) . I think I misread a different document and though a new feature had rolled out.. I thought I read if a \"App Service\" component was created in JSM, a Component was automatically created in Compass--- possibly thinking there had been a change with how the GitHub integration will now dynamically create a component when a new GitHub repo is created.\n\nThx\n" } ] } ]

[ "jira-service-management", "service" ]

[ { "author": "Kelvin T", "body": "Hello [@Luca Ferretti](/t5/user/viewprofilepage/user-id/5494282)\n\nI hope you are doing great. This is Kelvin from the Compass Support Team. Thanks for your question.\n\nIn order to further check this issue, I opened a ticket for you.\n\nPlease let me know if you have any questions.\n\nThank you!\n", "comments": null } ]

[ { "author": "Alastair Wilkes", "body": "Hey Matthew - sorry, but your image(s) didn't come through. Can you try adding them again?\n", "comments": null } ]

[ { "author": "Todd Schwartz", "body": "I have just become aware of Compass, so I'm not quite ready for a user experience interview. But I do have some feedback on a feature that concerns me: Dependencies. Compass appears to be designed for a human to manually enter and manage dependencies. I think this is problematic, because it would duplicate the dependencies that are already expressed in code. As the code continues to change, the manually entered dependencies would very easily become out of sync with the actual dependencies in the code.\n\nInstead, I suggest that Compass be designed to scan the project repo for key files that identify potential dependencies, e.g. requirements.txt or pyproject.toml for a python project. When Compass finds such potential dependencies, it could allow a human developer to confirm/correct/reject the dependencies. When a dependency is removed from the requirements.txt or pyproject.toml file, then Compass would automatically remove the associated dependency.\n", "comments": [ { "author": "Caylie Panuccio", "body": "Thank you for sharing your thoughts Todd! I will pass this onto the team.\n" }, { "author": "Taylor", "body": "Hey [@todd](/t5/user/viewprofilepage/user-id/4117696) glad you discovered Compass and thank you for jumping in with your feedback!\n\nI'd love to clarity a few things on dependencies and get your thoughts. Our goal with dependencies was to indeed design it for a human, but primarily to understand and navigate that information rather than manually input it.\n\nWe do allow for manual input of the values of course, however, to your point, depending on how complex the system is the need to automate quickly becomes paramount. We deal with a massive variety of customers and their internal systems and developer experience all have their nuances.\n\nFor the manual update, we do see a lot of teams actually just start by documenting their 'upstream dependencies' manually via key services so they can understand when their are deployments, incidents, and other events happening - this appears on the activity feed once you add dependencies.\n\nFor the automated side, we allow customers to add the dependency in their [\\`compass.yml\\` definition](https://developer.atlassian.com/cloud/compass/config-as-code/structure-and-contents-of-a-compass-yml-file/) which is usually automated by some bot/job their internal platform engineering team would setup. There are so many strategies for dependency management - maybe you have a proper service mesh effectively deployed and you are quite mature, you may use observability tools to look at API requests, or you may map dependencies in some kind of file in code.\n\nIn addition to [registering this in the \\`compass.yml\\` definition](https://developer.atlassian.com/cloud/compass/config-as-code/structure-and-contents-of-a-compass-yml-file/), you can also just use our public GraphQL API (which is available for every feature in the product) to interactive with the data model, dependencies included. Inside the [Update Component mutation](https://developer.atlassian.com/cloud/compass/graphql/#mutations_updateComponent) you can take whatever existing ways you use to detect dependencies and send that to Compass. We have an [open-source repo with several code snippets](https://github.com/atlassian-labs/compass-examples?tab=readme-ov-file) to help here but reach out to us if you need further help.\n\nOnce pushed into Compass, we try to focus on how developers will use this information. Today, we see customers using this for several different reasons\n\n1. **They use the activity feed to see upstream events (deployments/incidents, etc.) during development or incidents**. It helps an individual developer or team working on a single service understand the larger picture. These dependencies can cut across various component types - so the services, libraries, ML models, and other aspects that may change and they want to know about it.\n2. **During an incident**, they will see the affeted service(s) in Slack or in their incident management tool and will jump into the link to the Compass service. They will check the activity feed, and then jump into a couple of different dependencies to see more information about those component - who owns them, where the slack channel is, etc. This radically cuts down time to resolve as it let's developer self-serve and quickly find critical information.\n3. **Building a new feature**is increasingly involving multiple services/code bases that are assembled together to deliver some end value for the customer. Developers can use Compass to find popular services but also understand what THOSE services rely on and what tier it is. They would probably trust a Tier 0 service with 20 existing dependencies by other well-known services with lots of documentation than a Tier 3 service with no existing dependencies and no documentation. Furthermore, when they register that dependency, the team that owns the service providing the functionality can broadcast changes to all downstream consumers via announcements. This saves a TON of time and energy.\n\nThere is a lot more we want to do in tying these workflows together with JSW and JSM using the Automation platform and Notifications which we will continue to improve. But the bones are there.\n\nLastly - We have thought about building our own mechanism to 'auto-detect' dependencies and put that into a triage bay exactly how you have described! If we can find a flexible and performant way to do this that covers most customers' setups or preferences then we will absolutely prioritise it, we have just been focussed on a few other areas for the time being.\n\nWith that being said - [did you know we have a live marketplace to host various apps, using Forge, do extend Compass in an infinite number of ways](https://marketplace.atlassian.com/addons/app/compass)....building a small app to do this and hosting it on our marketplace would fill a needed gap right now. We will be offering paid apps in the near future. \n\nLet me know any further questions you have or general thoughts on this approach? When we circle back to an auto-detect feature, can we reach out to you?\n" } ] }, { "author": "Jaki3", "body": "Hi Caylie,\n\nThank you for reaching out. I'm interested in participating in the research session for Compass. The opportunity to share my experience and contribute to its improvement sounds great, and the e-gift card is a nice bonus.\n\nPlease let me know the next steps, and I'll be happy to answer the preliminary questions and schedule a time for the video conference. You can also visit my website [vista roofing lincoln](https://vistaroofinglincoln.co.uk/).\n\nCheers,\n", "comments": null }, { "author": "Manuel Niederkofler", "body": "hi,\n\ncan I also participate even if I am currently not using Compass.\n\nRegards\n", "comments": [ { "author": "Caylie Panuccio", "body": "Hi Manuel, thanks for checking! Unfortunately I do need people who use Compass for this study.\n\nHowever, if you'd like to participate in our research projects you can sign up to the Atlassian Research Group here: <https://www.atlassian.com/research-group>\n\nCheers,\n\nCaylie\n" } ] } ]

[ "feedback", "research" ]

[ { "author": "Alastair Wilkes", "body": "Hi Spencer, thanks for your question!\n\nBuild time and deployment time are derived from build and deployment events sent from GitHub via the GitHub/Compass integration. More details are here:\n\n<https://developer.atlassian.com/cloud/compass/integrations/integrate-Compass-with-GitHub/#supported-metrics>\n\nYou're correct that the integration looks for the environment tag to detect deployment events. The link above goes into this in a bit more detail.\n\nYou can see more info about other predefined metrics here: <https://developer.atlassian.com/cloud/compass/components/available-predefined-metrics/>\n\nFor the most part, you shouldn't *have* to do much to get things set up if you're using the out of the box integration (except check the environment name for deployments, as you pointed out). Let me know if you have any other questions!\n\nAlastair\n", "comments": [ { "author": "Spencer Robertson", "body": "Most of the metrics worked but was just struggling to see how they were generated to \"fine tune\" them (turns out some of our workflows had incorrect enviroment tags so the metrics were being thrown off)\n\nThis page really helped <https://developer.atlassian.com/cloud/compass/integrations/integrate-Compass-with-GitHub/#supported-metrics>. Thanks for that!\n" } ] } ]

[ "metric" ]

[ { "author": "YY Brother", "body": "Hi [@Matthias Moll](/t5/user/viewprofilepage/user-id/5103209)\n\nWelcome to our Community.\n\nI think you've asked a good question. I just tried it and we may need an automation rule to implement issue's auto assignment:\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/322083i6BBDEA60A8E8CE1A/image-size/large?v=v2&px=999 \"image.png\")\n\nHope it helps.\n\nThanks,\n\nYY?\n", "comments": null }, { "author": "Matthias Moll", "body": "Thank you for the reply. Surely you can do everything (a lot) with automation. I could solve it by:\n\n- create a custom field to the compass component defineing the 'default assignee'\n\n- introduce a post function after creation of an issue type which assigns the issue automatically to the default assignee of the first compass component which is assigned to the issue\n\nHowever, this would be more complex than working with the \"old\" components. I don't want to introduce new tooling that makes things more complicated that were previously simple. Does anyone have any other ideas?\n", "comments": null } ]

[ "assign" ]

[ { "author": "faraz rashdi", "body": "The naming convention needed for deploys to be picked up can vary depending on the deployment tool or system you are using. However, there are some common naming conventions that are often used to ensure deploys are picked up correctly:\n\n1. \\*\\*Semantic Versioning\\*\\*: Using semantic versioning for your deploy names can help organize and track different versions of your application. Semantic versioning typically follows the format \\`major.minor.patch\\`, where each part represents a different level of change in the software. For example, \\`v1.2.3\\` indicates major version 1, minor version 2, and patch version 3.\n\n2. \\*\\*Timestamps\\*\\*: Including timestamps in deploy names can provide a clear indication of when each deploy occurred. Timestamps are often formatted in a way that is sortable and easily readable, such as \\`YYYYMMDDHHMMSS\\` (year, month, day, hour, minute, second).\n\n3. \\*\\*Environment Indicator\\*\\*: Adding an environment indicator to deploy names can help distinguish between different environments, such as development, staging, and production. For example, you might use prefixes like \\`dev-\\`, \\`stage-\\`, or \\`prod-\\` to indicate the environment.\n\n4. \\*\\*Branch Name\\*\\*: Including the name of the branch being deployed can be useful for tracking changes and debugging issues related to specific branches. This is especially relevant in continuous integration/continuous deployment (CI/CD) workflows.\n\n5. \\*\\*Release Name or Tag\\*\\*: If your deployment process involves creating releases or tags in your version control system (e.g., Git), you can use the release or tag name as part of the deploy name. This helps link the deploy to a specific release or version of your application.\n\n6. \\*\\*Descriptive Labels\\*\\*: Including descriptive labels or identifiers in deploy names can provide additional context about the changes included in the deploy. This might include features, bug fixes, or other relevant information.\n\nHere's an example of a deploy name [incorporating](http://zakbags.com/products/louis-vuitton-favorite-bag-1) some of these elements:\n\n\\`\\`\\` \nv1.2.3-prod-20220501-143000 \n\\`\\`\\`\n\nThis deploy name indicates that it is version 1.2.3 deployed to the production environment on May 1, 2022, at 2:30:00 PM.\n\nIt's important to establish a consistent naming convention that works well for your team and aligns with your deployment process and tooling. Additionally, ensure that your deployment tool or system is configured to recognize and process deploy names according to your chosen convention.\n", "comments": null }, { "author": "Steffen Opel _Utoolity_", "body": "The [GitHub environment name mapping](https://developer.atlassian.com/cloud/compass/integrations/integrate-Compass-with-GitHub/#github-environment-name-mapping) documents the applied naming convention for the environment type, and it maps 'uat' to 'testing', i.e. it seems supported as such (the keywords are case insensitive):\n> The GitHub app for Compass evaluates the name of your [GitHub Environment](https://docs.github.com/en/actions/deployment/about-deployments/deploying-with-github-actions#using-environments) for all deployment events and uses a mapping to determine what environment type (Production, Staging, etc.) it falls into. We look for the presence of the below words within the name of the environment to determine the type.\n>\n> * production: \"production\", \"prod\", \"prd\", \"live\"\n> * staging: \"staging\", \"stage\", \"stg\", \"preprod\", \"model\", \"internal\"\n> * testing: \"testing\", \"test\", \"tests\", \"tst\", \"integration\", \"integ\", \"intg\", \"int\", \"acceptance\", \"accept\", \"acpt\", \"qa\", \"qc\", \"control\", \"quality\", \"uat\", \"sit\", \"canary\"\n> * development: \"development\", \"dev\", \"trunk\"\n>\n> In the case that an environment name matches more than one type, we use the order shown above to determine the mapping. For example, if your environment is named \"dev-prod\" we would map it to Production.\n\nThat being said, what you describe seems to indicate that your workflow isn't even recognized as a deployment in the first place - can you verify that the optional keyword *deployment* is present in your workflow? For example:\n\n jobs: deployment: runs-on: ubuntu-latest environment: uat steps: - name: deploy # ...deployment-specific steps\n", "comments": null } ]

[ { "author": "Carlos Garcia Navarro", "body": "Hi [@Janne Magnusson](/t5/user/viewprofilepage/user-id/5539452) ,\n\nWelcome to the Community! I'm trying to reproduce this issue and it's working for me. I added a few Jira epics linked to Goals and they consistently appear in the 'Jira' tab under the Goals section. Is this issue still happening? What browser are you using? Can you please check with a different browser? Are other users experiencing the same issue? Thanks,\n", "comments": [ { "author": "Janne Magnusson", "body": "Hi [@Carlos Garcia Navarro](/t5/user/viewprofilepage/user-id/1031232)\n\nThanks for your reply. I've tested again in Chrome and Edge, same result. One of my colleges also tested with the same result.\n\n/Janne\n" } ] } ]

[ "goals" ]

[ { "author": "jporinchukutty", "body": "Able to resolve the issue in Postman right now, modified content type as below and it worked.\n\nContent-Type - multipart/form-data; boundary=\\<calculated when request is sent\\>\n\nThanks\n", "comments": null }, { "author": "Fernando Eug?nio da Silva", "body": "[@jporinchukutty](/t5/user/viewprofilepage/user-id/5541696) , Welcome to the Atlassian Community!\n\nHave you added the special header: **X-Atlassian-Token: no-check**?\n\nThe documentation about add attachment in Jira mention this special header to be included in your REST API call: [The Jira Cloud platform REST API (atlassian.com)](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-attachments/#api-rest-api-3-issue-issueidorkey-attachments-post)\n\nAlso generally 500 errors are associated with not being able to call the application server, check if you are using the entire url complete with the HTTPS protocol\n", "comments": [ { "author": "jporinchukutty", "body": "Thanks [@Fernando Eug?nio da Silva](/t5/user/viewprofilepage/user-id/4606715) ,\n\nI do provide **X-Atlassian-Token: no-check,**but still same error, URL as well same, able to call other api's for get and put.\n\nPlease suggest for any other chance for this error code in postman.\n\nThanks\n" } ] } ]

[ "jira-api" ]

[ { "author": "Dave Rosenlund _Trundl_", "body": "Hi, [@Lakshmi C](/t5/user/viewprofilepage/user-id/11417) ?\n\nThe Bad News: The simple answer is, no. There is no way to share the same team structure from Atlas with other Atlassian products today.\n\nThe Good News: There is a pending enhancement Suggestion that you can vote for and follow (\"watch\") and a workaround contained in this Knowlege Base document:\n\n#### [Exporting Atlassian Teams and Members data from my Organization](https://confluence.atlassian.com/jirakb/exporting-atlassian-teams-and-members-data-from-my-organization-1364560115.html) {#toc-hId-346921295}\n\nI hope this helps,\n\n-dave\n", "comments": null } ]

[ { "author": "Steffen Opel _Utoolity_", "body": "The Atlassian Team has provided an accepted answer to a related question [Could not Connect to Microsoft Teams](https://community.atlassian.com/t5/Atlas-Group-questions/Re-Could-not-Connect-to-Microsoft-Teams/qaq-p/2668179/comment-id/505#M505):\n> It's a known issue after releasing Microsoft Teams v2. There is a problem in the desktop application, especially if a user is logged in several Microsoft Teams accounts.\n>\n> As a workaround to sign in to Atlas application, you can use [the browser version of Microsoft Teams](https://teams.microsoft.com/). After that, you can continue using the desktop Microsoft Teams application.\n\nThat being said, given you are experiencing the problem despite being supposedly addressed already, there might be other root causes in play still, as suggested in an [alternative answer](https://community.atlassian.com/t5/Atlas-Group-questions/Re-Could-not-Connect-to-Microsoft-Teams/qaq-p/2665987/comment-id/502#M502):\n> I had this same issue. It seems that, for us at least, it's because we have a GCC High 365 account and this is the reason it can't connect.\n", "comments": [ { "author": "Amandine Rimbert", "body": "Actually we figured out that this is due to privacy settings of the targeted MS Teams group. If the MS Teams group is public and I am not owner of it, then I am able to connect my Atlassian Home project to the needed Teams channel (provided that the channel is also public, and not private).\n" } ] } ]

[ { "author": "Christian", "body": "UPDATE: Ok, I ended-up spending another hour or two troubleshooting this and finally got the drop-down to autofill again... Whew!\n\nBut, it's not clear exactly what fixed it, I kept changing around my user groups, and ignored the yellow warning symbol about a user having multiple roles. I needed admin users to be able to have User access admin product roles, but also be able to use Jira, which apparently requires them to have User roles.\n\nThen there's something strange where, even if a user has full Jira admin and Org admin access, this drop-down feature will break, if there's not a lower-level access given (I guess), which is kinda strange in my opinion.\n\nDoes anyone know where a really good tutorial or guide is to Jira/Atlassian users and groups is, where it explains when your company needs a dozen custom groups to separate-out access per department, Managed accounts, and how to deal with default groups, etc.?\n", "comments": null }, { "author": "Drew McPayne", "body": "I finally found the answer to this issue in our system...\n\nI have no idea why, but somehow the global system permissions have changed - only a single group of users was enabled in 'Browse users and groups'.\n\nGoto\n\nSettings Cog in top right --\\> System![Jira User List issue 1.png](https://community.atlassian.com/t5/image/serverpage/image-id/346554i4C078E8095B4B4FC/image-size/large?v=v2&px=999 \"Jira User List issue 1.png\")\n\nGlobal Permissions --\\> Add the relevant user groups to the permission\n\n![Jira User List issue 2.png](https://community.atlassian.com/t5/image/serverpage/image-id/346555i1890F4513568EC83/image-size/large?v=v2&px=999 \"Jira User List issue 2.png\")\n\nIn my scenario, only Jira Developers were part of the permission, so admins couldn't browse groups etc in the user management groups view :O\n", "comments": null }, { "author": "Trudy Claspill", "body": "Hello [@Christian](/t5/user/viewprofilepage/user-id/5534414)\n\nWelcome to the Atlassian community.\n\nWhen I start to type in the name of a group, initially it shows as an email address but then quickly switches to showing the group names that match. At the bottom of the list is the email address it was trying to construct.\n\n![Screenshot 2024-07-02 at 3.02.26?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/333132iC076ED09931D91E4/image-dimensions/338x348?v=v2 \"Screenshot 2024-07-02 at 3.02.26?PM.png\")\n\nAre you sure what you are typing in matches to a group that has access to the site?\n", "comments": [ { "author": "Christian", "body": "Hi [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011)\n\nThanks for your reply and great to be in the Atlassian community.\n\nWhat you describe and what your screenshot shows is exactly how it used to work, but atlas, for the last week the auto-filling stopped filling-in the groups or anything else besides the default email, and I've left it up waiting for a while and it never loads anything else as it used to.\n\nSee attached similar screenshot as you have done... This is one Jira project that is side-by-side with another Jira project that has groups starting with \"app-\", but as you can see from the screenshot it only has groups I added a month ago, but doesn't auto-fill the drop-down with any of my other app groups.\n\n![jira-issue.png](https://community.atlassian.com/t5/image/serverpage/image-id/333320i9FD1F54440AA8C51/image-size/large?v=v2&px=999 \"jira-issue.png\")\n" }, { "author": "Christian", "body": "In fact... the moment I start entering anything into that \"Names or emails\" field, which used to take Group names without any issues... I get the following...\n\nWhich appears to be some sort of GET request to a RESTful API endpoint for \"groupuserpicker\" but it results in an HTTP 403 error (forbidden).\n\n* The \"app-\" groups have access to the Jira product.\n* The \"app-\" groups are in other Jira projects (from when I could add them).\n* I can add users from that group individually, if I copy the email address.\n* Nothing special about advanced permissions, should be close to default.\n* Nothing special about browser, just latest Chrome 126.0.6478.61 on macOS.\n\nSee attached screenshot from browser inspection panel...\n\n![group-user-picker.png](https://community.atlassian.com/t5/image/serverpage/image-id/333331i58CCFF5584FF347F/image-size/large?v=v2&px=999 \"group-user-picker.png\")\n" }, { "author": "Trudy Claspill", "body": "Have you tried the same steps in another browser application or a private browser window?\n\nDo other admins with the same permissions have the same experience?\n" }, { "author": "Christian", "body": "[@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011)\n\n* Yes, definitely other Jira and Org admins; that's what started me to create the first support ticket and this community question.\n* I just tried a new Incognito/private window in Chrome, which does have the exact same issue/s.\n* I just tried it in Firefox 127.0.2 and attached is its console errors...\n\n![firefox-jira-issue.png](https://community.atlassian.com/t5/image/serverpage/image-id/333341iF44C75BE48A441B3/image-size/large?v=v2&px=999 \"firefox-jira-issue.png\")\n" }, { "author": "Blake McLeod", "body": "Did you ever get to a resolution for this? We're experiencing the same issue. I was consolidating our groups, removed all the old ones but now I can't add the new user groups.\n\nVery frustrating because now none of our staff can access the tickets...\n" }, { "author": "Christian", "body": "[@Blake McLeod](/t5/user/viewprofilepage/user-id/5568767)\n\nYes, it was basically a permissions issue, and was not intuitive, but I finally ended-up changing around the user groups enough and ignored the yellow warning symbols about a user having multiple roles (which in most systems you would avoid), and then added lower level permissions, even though these were admin users, or users with admin product roles. So, even if a user has full Jira admin and/or Org admin access, this drop-down feature will break, so, if there's is not that lower-level access given it won't show. Hope that helps!\n" }, { "author": "Blake McLeod", "body": "Awesome, that fixed it for me too. I added every role under the sun to my account and I was able to finally add groups to my the project I was an owner of.\n" }, { "author": "Trudy Claspill", "body": "This came up recently with a colleague of mine consulting for a client.\n\nMy colleague discovered that the person trying to add groups to roles in a project needed to have the global permission for Browse User and Groups.\n" } ] } ]

[ "cloud", "jira", "jira-cloud" ]

[ { "author": "Amanda Barber", "body": "Hi, [@Shepherd Moore, Jen (J.A.)](/t5/user/viewprofilepage/user-id/4840243) - in [this recent community post](https://community.atlassian.com/t5/Atlas-questions/I-want-to-use-JQL-to-interact-with-Atlas-Is-it-possible/qaq-p/2664894) it sounds like JQL doesn't work with Atlas yet.\n\nQuoting [@Ste Wright](/t5/user/viewprofilepage/user-id/1166470)\n> Atlas doesn't support JQL at this stage.\n>\n> Atlassian confirms that in [this answer](https://community.atlassian.com/t5/Atlas-questions/Re-Is-it-possible-to-query-Atlas-records-using-JQL-terms/qaq-p/2417706/comment-id/509#M509), which also has some other options using URL parameters...\n> > 1. Atlas doesn't natively support \"advanced search\" *but* all searches are backed by something called TQL (Team Query Language). The search filters that are available are all translated to TQL - we just don't expose a way for you to type it in.\n> >\n> > 2. That said, you can enter parameters in the URL if you're very keen.\n> >\n> > 3. Otherwise if you just want to search for a specific project or goal key, you can enter the key in search and it will show up.\n>\n> ---\n>\n> You could suggest this though as a new feature request? You can do this through here: <https://jira.atlassian.com/secure/Dashboard.jspa>\n", "comments": [ { "author": "Shepherd Moore, Jen (J.A.)", "body": "Hi Amanda! Totally got it on Atlas. \n\nI'm looking, though, to do the JQL within Jira itself to reflect where \"Goals\" have been linked. \n\nSo - I would not expect to query in Atlas. \n\n<br />\n\n\"Linked Goals\" in Jira itself is what I want to query, and have a list of issues return.\n" }, { "author": "Amanda Barber", "body": "Sorry that I misunderstood your question!\n\nI do see Atlas Goals for filtering issues, but in JQL that is just a custom field, so it seems you might be able to use that. For some reason, my instance has multiple \"Atlas Goals\" custom fields which has sent me down a rabbit hole... ?\n" } ] } ]

[ "jql" ]

[ { "author": "Eugenio Onofre", "body": "Hi [@?????? ???? ?????? ????????](/t5/user/viewprofilepage/user-id/5417825),\n\nWelcome to the Atlassian Community. \nThis seems to be an error with the system itself.\n\nI would recommend raising a support request with the Billing team at <https://support.atlassian.com> so they can check and process your payment.\n\nPlease remember to accept this answer as it may also help other community members in the future.\n\nRegards, \nEugenio\n", "comments": [ { "author": "?????? ???? ?????? ????????", "body": "in which one ? can you tell me more details\n" } ] } ]

[ { "author": "Rudina Aldubayan", "body": null, "comments": null } ]

[ "block", "cloud", "due-date", "priority" ]

[ { "author": "Jack Brickey", "body": "Please share a screenshot of what you see. Have you ever successfully logged in? Are others able to login successfully?\n", "comments": null } ]

[ { "author": "Nic Brough -Adaptavist-", "body": "Welcome to the Atlassian Community! \n\nI think you are in the wrong place, your question does not seem to be about an Atlassian system. I suspect you have clicked on \"help with the system in use for documentation or issue tracking\" instead of \"help with the product\".\n\n(Oh, and there is no such thing as \"google bitcoin\")\n", "comments": null } ]

[ { "author": "Jack Brickey", "body": "Hi [@thariq mohamed](/t5/user/viewprofilepage/user-id/5407550) ,\n\nI think you may be in the wrong place for support. This community is associated with support for Atlassian products.\n", "comments": [ { "author": "Jack Brickey", "body": "it could be that you arrived here as a result of a Atlassian product link within the support portal for planSwift. It might be that they use Atlassian's Jira service management for support.\n" } ] } ]

[ { "author": "Nic Brough -Adaptavist-", "body": "Welcome to the Atlassian Community!\n\nYou probably need to ask the administrators of your Emeter community.\n\nWe're the Atlassian community, not Emeter (although I did do a bit of work with a company called Emeter, who may have had their own Community, so, unusually, I might actually know who your admins are. Assuming they've not moved in the last 5 years)\n", "comments": [ { "author": "Marcello Ferraro", "body": "thanks!\n" } ] } ]

[ "unknown-hosting-type" ]

[ { "author": "Eugenio Onofre", "body": "Hi [@Riyaben Agrawal](/t5/user/viewprofilepage/user-id/5389136)\n\nWelcome to the Atlassian Community.\n\nThe Assist app logo is default from the Assist and hence we, from the community, are not able to assist with this investigation as we do not have access to customer instances.\n\nI would recommend raising a support request with Atlassian Support team at <https://support.atlassian.com>\n\nPlease do not forget to accept this answer in case it helps you resolve your question so it can help other community members in the future.\n\nRegards, \nEugenio\n", "comments": null }, { "author": "Riyaben Agrawal", "body": "Thanks you eugenio. I'll contact them.\n", "comments": null } ]

[ "cloud" ]

[ { "author": "Andy Heinzer", "body": "Hi [@??????? ???????](/t5/user/viewprofilepage/user-id/5377828)\n\nI believe that your account is being blocked due to your email address domain ending in a .ru top-level domain. Even if your IP address is not located within Russia or Belarus, your domain technically is based in Russia.\n\nTry creating an account that doesn't use a .ru address for your email. If you're still getting blocked, try reaching out using <https://www.atlassian.com/company/contact/purchasing-licensing>\n\nThis link should put you in contact with our advocate team that can better help here.\n\nAndy\n", "comments": null }, { "author": "Jack Brickey", "body": "Hi [@??????? ???????](/t5/user/viewprofilepage/user-id/5377828) ,\n\nI will flag for Atlassian input.\n", "comments": null } ]

[ "atl-rvw" ]

[ { "author": "Nic Brough -Adaptavist-", "body": "Welcome to the Atlassian Community!\n\nYou will need to explain more. What work log? Where is it?\n\nWhat are the symptoms of \"can not open\"? No option to click? Click does nothing? Error message? Large Penguin sleeping on your keyboard so you can't use the computer?\n", "comments": null } ]

[ { "author": "Ai Hirama", "body": "?????????????????????????\n\n??????????Free????????????????????????????????????????????????????????????????????????????????????????????\n\n?????????????????????????????????????????????????????????????????????????????????????????\n", "comments": [ { "author": "????", "body": "??????????????\n\n?????????????????????????????????????????????????\n\n???????????????\n" } ] }, { "author": "Emel Do?rus?z", "body": "Hello,\n\nSince Halp is not available anymore, you may want to use Actioner's ticketing solution instead:\n\n<https://actioner.com/solutions/help-desk>\n\n<https://actioner.com/support-use-cases>\n\n<https://actioner.com/app-directory/conversational-ticketing-with-zendesk-47>\n\nYou can connect it to your ticketing tools like Jira Service Management or Zendesk, or use the standalone version. And run all your ticketing and service management actions from Slack. Let me know if you need any help.\n\nThanks,\n\nEmel Dogrusoz\n\nCo-founder @ [Actioner](http://www.actioner.com)\n", "comments": null } ]

[ "cloud" ]

[ { "author": "Tim Kopperud", "body": "[@Huaning_Gu](/t5/user/viewprofilepage/user-id/5340033), welcome to the community.\n\nDo you have the oppertunity to attach an image of what you see after login (remember to obscure private information).\n\nTimK.\n", "comments": null } ]

[ { "author": "Tomislav Tobijas", "body": "Hi [@Jhorelle Mendoza](/t5/user/viewprofilepage/user-id/5336533)\n\nBy the look of the screenshot, this would mean that the portal/project is configured in a way so that agents can add announcements to the portal. If you wish to configure the portal name, description or logo, you would need to be **project administrator** in order to do so by following the [instructions](https://support.atlassian.com/jira-service-management-cloud/docs/brand-your-portal/).\n\nOn the other hand, if you wish to configure the help center (what you mentioned there, to be able to see ***Configure*** button) you need to be **Jira administrator** . You can read more [here](https://support.atlassian.com/jira-service-management-cloud/docs/what-can-i-customize-about-the-help-center/).\n\nOne more thing - Halp is actually ex. product (now Assist) so this is not actually a 'help' group but I can see people often write general questions about other products.\n\nBest regards, \nTom\n", "comments": [ { "author": "Jhorelle Mendoza", "body": "Thank you so much for your response. Regarding the Project administrator. I already have the permission for that one and I am still unable to customize and also I don't have the access for the look and feel. And advise?\n\n![Screenshot 2023-10-09 at 1.52.50 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/285285i1AAAE198F5BFB1A9/image-size/large?v=v2&px=999 \"Screenshot 2023-10-09 at 1.52.50 PM.png\")\n" }, { "author": "Tomislav Tobijas", "body": "As a project administrator, can you navigate to **Project settings \\> Portal settings** ?![2023-10-10_09-04-53.png](https://community.atlassian.com/t5/image/serverpage/image-id/285328iA326E3B24A9C65E0/image-size/large?v=v2&px=999 \"2023-10-10_09-04-53.png\")\n\nRegarding **++help center++** ++look and feel++ , as stated above, you will need to be **Jira administrator** in order to view that option.\n" }, { "author": "Jhorelle Mendoza", "body": "Hello , Yes I can navigate portal settings , But that's gonna be it.\n\nAs mentioned, I am an administrator already but I am unable to customize and have access with the look and feel.\n\nAre you saying that **Jira service management administrator** is different from **Jira administrator**?\n\n![Capture.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/285338i4DEAEFE61D608AF0/image-size/large?v=v2&px=999 \"Capture.PNG\")![Untitled.png](https://community.atlassian.com/t5/image/serverpage/image-id/285339i832910C980B7D499/image-size/large?v=v2&px=999 \"Untitled.png\")\n" }, { "author": "Tomislav Tobijas", "body": "Jira administrator covers the administration part for all Jira products. Can you confirm that you can navigate to **Settings \\> Products** . If not, that would mean you are not Jira administrator and therefore cannot see options to configure the help center look \\& feel.![2023-10-10_11-38-06.png](https://community.atlassian.com/t5/image/serverpage/image-id/285348iB01F0BD76C4CB9B6/image-size/large?v=v2&px=999 \"2023-10-10_11-38-06.png\")\n" }, { "author": "Jhorelle Mendoza", "body": "This is all I see in here. Does that mean that I am not a Jira Administrator? If so? How can I have access on that? Can we have multiple administrators on Jira? Please advise.\n\n![Capture.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/285351i839A6EB76EB00D7B/image-size/large?v=v2&px=999 \"Capture.PNG\")\n" }, { "author": "Tomislav Tobijas", "body": "Hi [@Jhorelle Mendoza](/t5/user/viewprofilepage/user-id/5336533)\n\nYes - by the look of the screenshot that would mean you are not in fact Jira administrator. Please contact your Jira administrator to request administrator rights (you can contact them via organization channels or via that form link you can see in the yellow panel once you open **Settings** menu).\n\nTo answer this question:\n> *Can we have multiple administrators on Jira?*\n\nYes - you can have unlimited number of Jira administrators, however, it is recommended to keep that number to a minimum.\n" }, { "author": "Jhorelle Mendoza", "body": "[@Tomislav Tobijas](/t5/user/viewprofilepage/user-id/3848395) Hello Again!\n\nIs there a way that I can modify/edit this form? \nI want to add some information that tells my client to make sure to create a loom video recording and send us the link when submitting a ticket. Is there a way?\n\n![Screenshot_2023-10-24_at_1.10.34_PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/288091iCE69DE2EB23ECEF1/image-size/large?v=v2&px=999 \"Screenshot_2023-10-24_at_1.10.34_PM.png\")\n" }, { "author": "Tomislav Tobijas", "body": "Hello [@Jhorelle Mendoza](/t5/user/viewprofilepage/user-id/5336533) !\n\nFrom what you've described, I would suggest trying out [forms in Jira Service Management](https://support.atlassian.com/jira-service-management-cloud/docs/use-forms-in-jira-service-management/). Basically, you could create a form with only an informational part or with all fields the same as in the form from the screenshot. Once you create the form, you can connect it with request type(s) where in the example above, that would be request type **Technical support**.\n\nIn the example below, you can see that I've added *note panel* with some content and also *Description* field description with some content. You can choose any of the two.\n\n![2023-10-24_21-44-53.png](https://community.atlassian.com/t5/image/serverpage/image-id/288099i6E3539D3DA4D5EAF/image-size/large?v=v2&px=999 \"2023-10-24_21-44-53.png\")\n\nAdditionally, if you don't want to use forms, you can simply navigate to Project settings \\> Request types \\> \\*select request type and then just change the display description for some field (e.g., \"Description\" field).\n\n![2023-10-24_21-47-46.png](https://community.atlassian.com/t5/image/serverpage/image-id/288100i5DA1A21EB7905A4A/image-size/large?v=v2&px=999 \"2023-10-24_21-47-46.png\")\n\nHope this helps!\n\nBest, \nTomislav\n" }, { "author": "Jhorelle Mendoza", "body": "Thanks again for your help!\n" } ] } ]

[ "cloud" ]

[ { "author": "Matthias Gaiser _K15t_", "body": "Hi [@NOC TEAM](/t5/user/viewprofilepage/user-id/5305832)\n\nwelcome to the Atlassian Community.\n\nYou've posted your request to a public site where volunteers and Atlassians try to help you. However, we can't help you in getting access to the site. I'd advice you to reach out to your Jira Administrator, to the [Atlassian Support](https://support.atlassian.com/contact/#/) or describe your problem in more detail, e.g. are you the admin of that instance?\n\nCheers, \nMatthias.\n", "comments": null } ]

[ "unknown-hosting-type" ]

[ { "author": "Tomislav Tobijas", "body": "Hi [@Saad Mehmood](/t5/user/viewprofilepage/user-id/5311068)\n\nI would suggest contacting [Atlassian Support](https://support.atlassian.com/) regarding this issue. Most likely it is the case that the email address is marked as \"Bounced\" and they would need to clear email/user from the bounce list.\n\nCheers, \nTom\n", "comments": [ { "author": "Saad Mehmood", "body": "Hi [@Tomislav Tobijas](/t5/user/viewprofilepage/user-id/3848395) \n\nThanks for your response. I am able to receive email notification related to atlassian community portal. If my email is marked as \"Bounced\" then I should not be able to receive any email notification from any atlassian service, right?\n" }, { "author": "Tomislav Tobijas", "body": "I cannot confirm or deny that. In my opinion/experience, these two are ++not++ 'connected' but I cannot be sure. Would be great if anyone would clarify that here, or if you'll raise a ticket to Atlassian Support [@Saad Mehmood](/t5/user/viewprofilepage/user-id/5311068), you could ask them that as well (if they provide the answer, please share it here).\n\nMy initial reply was based on my/our experience we had we our clients where that issue you mentioned was caused due to system bouncing email for that specific user email address. Again, we're only talking about trying to reset the password using the link from the User Directory in the Admin Hub.\n" }, { "author": "Saad Mehmood", "body": "Thanks [@Tomislav Tobijas](/t5/user/viewprofilepage/user-id/3848395) , I have created a ticket on Atlassian Support. I\n" }, { "author": "Saad Mehmood", "body": "My email was blocked on their end. So, they have removed my email from blocker list and now I am able to reset my password.\n" }, { "author": "Muhammad Humayun", "body": "Same happen with my colleague's email. \nI'm receiving (from the same email domain) the recovery email but my colleague not. \nAnd the support is not actively taking request, cause I can not submit any queries. \nLooks like that email address has been blocked by Atlassian \nShall I mention the email here? \nMay I help through this platform?\n" }, { "author": "Naeemah Steward", "body": "what is the recovery link eemail address so I can add this to the safe list\n" }, { "author": "Muhammad Humayun", "body": "Here you [@Naeemah Steward](/t5/user/viewprofilepage/user-id/5485390) go with the email below\n\n```\[email protected]\n```\n" } ] } ]

[ { "author": "Andy Heinzer", "body": "Hi [@Greg Moseley](/t5/user/viewprofilepage/user-id/5296238)\n\nSorry to hear about this. Is it possible that you received a spam message from an atlassian.net site? If you did, then it's possible that account could have been created that references your email address. However when I did a lookup on your email address, I don't see any messages sent to it before 2023-08-18T20:54:02.000Z and I suspect this is the first message we send when you complete the account creation.\n\nWith some email providers such as gmail, it's possible that a spam message was sent to your account in a format such as [email protected] If that happens, the account [email protected] gets that message delivered to it. If you still have such a spam message that you received from us, please let me know the specific email address it was sent to, this way I can make sure that the abusive site has been shut-down.\n\nAlternatively, you can also forward any spam message received from an Atlassian site directly to [email protected] however that inbox is not able to respond directly to reports sent to it.\n\nAndy\n", "comments": null }, { "author": "Jack Brickey", "body": "Hi [@Greg Moseley](/t5/user/viewprofilepage/user-id/5296238) , this forum is a support forum for all Atlassian products. It is tied to your Atlassian account. To be clear it is not a scam. With that said I have flagged your post to have someone from Atlassian assist you. Cheers!\n", "comments": null } ]

[ "atl-rvw" ]

[ { "author": "Ian Winter", "body": "Not an answer I'm afraid, but, I have the same issue. I've got a slack workflow posting via jira cloud plugin however no matter what formatting I try it just turns up as plain text! \n\nEven \\*bold\\* won't render.\n", "comments": null }, { "author": "Kalpana Chinnappan", "body": "Same here, bold text does not render. Text formatting in general does not work when adding a Jira issue description via the Jira Cloud Slack workflow step.\n", "comments": null } ]

[ "cloud" ]

[ { "author": "Hermance NDounga", "body": "Hello,\n\nIf you click on Fields, select a field and in the formatting options, check \"highlight row and cards\", your matrix bubbles will be color coded\n\n![Screenshot 2024-09-18 at 15.04.51.png](https://community.atlassian.com/t5/image/serverpage/image-id/347946iB8D860B11D216A53/image-dimensions/269x373?v=v2 \"Screenshot 2024-09-18 at 15.04.51.png\")\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n", "comments": null } ]

[ "cloud", "jira-product-discovery" ]

[ { "author": "Hermance NDounga", "body": "Hey Sahil,\n\nTeams aren't yet in Jira Product Discovery. I suggest to post your message in the dedicated developper forum : <https://community.developer.atlassian.com/>\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n", "comments": null } ]

[ { "author": "Nikola Perisic", "body": "Hello [@etalase visuals](/t5/user/viewprofilepage/user-id/5591708)\n\nThis is probably due to the default personal setting\n\n![Screenshot from 2024-09-14 21-12-41.png](https://community.atlassian.com/t5/image/serverpage/image-id/347416i1862BF174D30F7B2/image-size/large?v=v2&px=999 \"Screenshot from 2024-09-14 21-12-41.png\")\n\nYou can always toggle these off.\n", "comments": null } ]

[ { "author": "Jet", "body": "Hi [@Matt Allen](/t5/user/viewprofilepage/user-id/5273145)\n\nYou could use a single JPD project that has multiple sections and views by product/team/craft.\n\nThis is also how we set it up for our Atlassian Growth team that works on multiple products.\n\n**1. Create a section for each product**\n\n**![Screenshot 2024-09-16 at 11.40.06?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/347497i277C54047A7CA247/image-size/large?v=v2&px=999 \"Screenshot 2024-09-16 at 11.40.06?AM.png\")**\n\n**2. Create views within each section**\n\nFor example, as a PM I want to create a high level (now, next, later) roadmap that I can share with my stakeholders. To do that I *create a new board*grouped by now, next later (and add a label to the ideas to filter by now/next/later)\n\n![Screenshot 2024-09-16 at 11.39.09?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/347500i91DAA43F11F044A5/image-size/large?v=v2&px=999 \"Screenshot 2024-09-16 at 11.39.09?AM.png\")\n\nYou Engineering counterpart probably wants to see the roadmap on a timeline, so you could create a a timeline view for that within each section\n\n![Screenshot 2024-09-16 at 11.49.10?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/347502iC697C4B2AA2929AC/image-size/large?v=v2&px=999 \"Screenshot 2024-09-16 at 11.49.10?AM.png\")\n\n**3. Create an ideas backlog filtered by team to collaborate on prioritisation**\n\nI recommend creating an ideas backlog for each product, organised by feature/focus area, which allows you to prioritise your roadmap as a team (together with engineering)\n\nHere's an example of what that could look like\n\n* Create themed list view that shows ideas with prioritisation criteria/scoring. You can drag ideas around to list them in order of priority.\n\n![Screenshot 2024-09-16 at 11.56.53?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/347504i4638EE081D1BA36D/image-size/large?v=v2&px=999 \"Screenshot 2024-09-16 at 11.56.53?AM.png\")\n\n* Once you have done the high level prioritisation with you eng/design counterparts, you can create a board view like this that's easier to read and allows you to easily see the top priorities and re-prioritise if needed. Again, you could do this for all your products/features.\n\n![Screenshot 2024-09-16 at 11.53.08?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/347503iDEC11D1C8CAD7900/image-size/large?v=v2&px=999 \"Screenshot 2024-09-16 at 11.53.08?AM.png\")\n\nHope this helps! Happy to answer any other questions\n\nCheers,\n\nJet\n", "comments": [ { "author": "Tanguy Crusson", "body": "Hi [@Matt Allen](/t5/user/viewprofilepage/user-id/5273145) : what [@Jet](/t5/user/viewprofilepage/user-id/397079) shared above ?\n\nAlso, you'll find some answers for this in the Jira Product Discovery handbook, in particular the [Prioritization](https://pm-dev.atlassian.net/wiki/external/ZWFjOTNkMThiZTY1NGY2MmFlODQ0MTAyNDM5MmE4YTg) and [Roadmapping](https://pm-dev.atlassian.net/wiki/external/OGY3MmI5ZTFhYWEwNDk4NjhhZTM3YzkwMTUyMjMwYzk) sections.\n" } ] } ]

[ "cloud", "jira", "jira-cloud" ]

[ { "author": "Tanguy Crusson", "body": "Hi [@Josh](/t5/user/viewprofilepage/user-id/5591327) - we haven't added translations for the templates yet. Something on the todo list!\n", "comments": null } ]

[ "deutsch", "german" ]

[ { "author": "Simon Rimbert", "body": "Figured this out on my own. I can modify the things, and the Update button becomes clickable after I've made a change. So the default setting of the window is editing mode, in a way.\n\nI don't reckon that's intuitive haha.\n\nCheers\n", "comments": null } ]

[ "status", "workflow" ]

[ { "author": "Jet", "body": "Hi [@Snorre Strand Asbj?rnsen](/t5/user/viewprofilepage/user-id/5473273)\n\nIt sounds like you are using Jira Plans to track initiatives? We are currently working on the Jira Plans x JPD integration <https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Early-Access-Program-new-integration-with-Jira-Plans-ex-Advanced/ba-p/2743110>\n\nThis first version of the integration allows you to link initiatives to ideas, with some limitations, like only seeing the key issues and summary, no other fields just yet. We plan to improve the integration based on feedback (see community post), so soon you will be able to see specific fields between the two.\n\nIn the meantime, you can follow [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313) advice (thanks [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)\n", "comments": [ { "author": "Jet", "body": "We also have automation templates if you purely want to automate the global fields between your delivery tickets and JPD ideas\n\nHere's how you can do that <https://support.atlassian.com/jira-product-discovery/docs/manage-automation-templates/>\n" } ] }, { "author": "Bill Sheboy", "body": "Hi [@Snorre Strand Asbj?rnsen](/t5/user/viewprofilepage/user-id/5473273)\n\nShort answer: that is likely possible.\n\nFirst, Jira Product Discovery (JPD) projects have Idea issue types, and those have specialized link types to \"delivery tickets\". Those delivery tickets are normally Jira Software Project (JSP) issues, allowing visibility of delivery progress.\n\nNext, a project-scope rule can create issues in other projects (e.g., a rule in a JPD project creates an issue in a JSP project), but it cannot access them otherwise. To access or update issues in another project, a rule must have multiple-project or global scope. Your Jira Site Admin will need to manage such rules in the global admin functions.\n\nNext, and from my perspective, a JPD project is a special type of team-managed project (TMP), and so the field types and configurations are different. For many fields it is possible to use automation rules to move / copy data back and forth with a JSP project's issue. The \"trick\" is understanding the underlying structure of the JPD Idea fields so the data can be moved. One exception is the Calculated Field type in JPD: those are set based on values in Ideas and cannot be set by rules.\n\nFinally, please consider that rules could have errors or fail to run when expected (e.g., such as during an Atlassian outage). Please consider creating a test, free Jira site (or use a sandbox) to fully exercise your configuration and rules before using them in production. And, consider how to \"catch up\" if rules do not run when expected.\n\nKind regards, \nBill\n", "comments": null } ]

[ "cloud", "jira", "jira-cloud", "jira-product-discovery", "link" ]

[ { "author": "Tanguy Crusson", "body": "Hi Rebecca, I assume you mean for the board view, for each board column? That is not possible currently. Could you please send a screenshot to [email protected] so we can see how bad this is for you? Thanks!\n", "comments": null } ]

[ "fields", "view" ]

[ { "author": "Tanguy Crusson", "body": "Hi Rebecca, that is not possible currently - the comment field just shows the number of comments (and if there are new ones you haven't seen yet).\n\nWhat do you put in comments? Status updates?\n", "comments": [ { "author": "Rebecca Graf", "body": "[@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) yes, we wanted to use it for status updates. Today, we are doing this with a dedicated field but that means, that we always have to overwrite the last entry. We'd prefer to keep the history of those status updates available in the ticket (without switching to the history).\n" }, { "author": "Tanguy Crusson", "body": "OK I see, thank you.\n\nI can't really see another option than the dedicated field today. There are a few things we're exploring for later, but it's too early to share.\n" }, { "author": "Rebecca Graf", "body": "I will stay tuned ;-) Thanks for your fast response anyways.\n" } ] } ]

[ "comments", "field", "list-view" ]

[ { "author": "Tanguy Crusson", "body": "Hi [@mm_ambrogi](/t5/user/viewprofilepage/user-id/4788194) , would you mind doing a screen recording (e.g. Loom) and sending it to [email protected]? So I can see what's going on.\n", "comments": null } ]

[ { "author": "Mart Postma", "body": "Hi Claire, \n\nI believe that this is what you are looking for: \n![status mapping Jira to JPD.png](https://community.atlassian.com/t5/image/serverpage/image-id/346793i18A4E940CD36ED98/image-size/large?v=v2&px=999 \"status mapping Jira to JPD.png\") \n\nNot sure if this is still the easiest way to do so, but it's been working great for us.\n\nPlease note that we have copied this automation rule for all status mappings that we want from Jira to JPD. I guess you could also create a single automation rule which triggers on a status transition and then branches through different IF-statements based on the mapping you configure.\n\nHope it's of help to you!\n", "comments": [ { "author": "Adrian_Lester", "body": "Adding a comment at the end of an automation is a really nice touch, I'd never thought of that. Thanks for sharing this!\n" }, { "author": "Tanguy Crusson", "body": "[@Claire Holmes](/t5/user/viewprofilepage/user-id/5458943) from the [FAQ](https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Frequently-asked-questions-about-the-product-how-do-I/ba-p/2002378), I think this should be relevant:\n\n**How do I automatically change an idea when its delivery issues are done?**\n\nYou can use Project Automation to automatically change an idea (e.g., change a field value, transition to a status) when its delivery epics/issues are done.\n\n[Demo: project automation in Jira Product Discovery](https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Product-demo-Automation-for-Delivery/ba-p/2057152)\n" }, { "author": "Claire Holmes", "body": "Thanks I will try this out!\n" } ] } ]

[ { "author": "Tanguy Crusson", "body": "Hi Levi, to get the list of delivery tickets, you need to get the list of linked issues (that's how it's stored). They are linked using a specific issue link type.\n", "comments": [ { "author": "Levi Palmer", "body": "Thanks [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) that works! After playing with the API results, I was able to pull them by looking for linked issues with the link type \"Polaris issue link.\" Not sure what that means exactly, but it seems to be the unique link type for JPD \\<\\> Jira Delivery tickets, since I wanted to make sure I only use delivery tickets in my code and not pull in other kinds of linked tickets.\n" }, { "author": "Tanguy Crusson", "body": "Awesome. Yes that's the name of the link type (very obscure - back from when JPD was called \"Polaris\" - we need to clean that up at some point)\n" } ] } ]

[ "api" ]

[ { "author": "Nick H", "body": "Hi [@Rebecca Graf](/t5/user/viewprofilepage/user-id/3020706) ,\n\nAn automation like that one below should work for the use case - which uses multiple IF / ELSE components to map each JPD status to Jira status:\n\n![status1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/346634i8DF836A008EB9392/image-size/large?v=v2&px=999 \"status1.jpg\")![status2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/346635iC81485F4D59B1351/image-size/large?v=v2&px=999 \"status2.jpg\")\n\n1) WHEN: Issue transitioned\n\n2) IF / ELSE\n\n* Status = \"JPD status A\"\n\n3) Branch rule / related issues\n\n* Type of related issues = Linked issues\n* Link types = is implemented by\n\n4) THEN: Transition the issue\n\n* Destination status = \"Jira project X, status B\"\n\n5) IF / ELSE\n\n* Status = \"JPD status C\"\n\n6) Branch rule / related issues\n\n* Type of related issues = Linked issues\n* Link types = is implemented by\n\n7) THEN: Transition the issue\n\n* Destination status = \"Jira project X, status D\"\n\n\\^ And so on depending on how many JPD idea statuses you want to map to Jira issues statuses.\n\nSo each *IF / ELSE* component should be tied to the top *WHEN: Issue transitioned* component, and each *IF / ELSE* component branches after to look for the delivery ticket.\n\nIf an *IF / ELSE* component does not match (Ex: steps 2-4 above), the automation will then check the following (Ex: steps 5-7 above), and so on, until a there is a match - then stop reviewing the following *IF / ELSE* components after the match.\n\nHope that helps! Let us know if you have any questions.\n", "comments": [ { "author": "Rebecca Graf", "body": "Hi [@Nick H](/t5/user/viewprofilepage/user-id/2540930) , thank you so much for your explanation, that definitely helps.\n\nJust one more question: Would it be possible to run this automation without a specific trigger (step 1) but on a daily basis? There can be usecases, where we'll have a mismatch between the two tools and I'd like to cover them as well (without waiting for a transition in JPD).\n\nHaven't done anything like this before and didn't find an explanation how to run an automation regularly without trigger.\n\nBest regards\n\nRebecca\n" }, { "author": "Nick H", "body": "Hi [@Rebecca Graf](/t5/user/viewprofilepage/user-id/3020706) ,\n\nYes I believe that should be possible with something like this is as the main trigger instead:\n\n![sched1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/346854iA4E7F51EC0499897/image-size/large?v=v2&px=999 \"sched1.jpg\")![sched2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/346855iC13A33D72A9A8F9E/image-size/large?v=v2&px=999 \"sched2.jpg\")\n\n\\^ Where the automation is scheduled to run daily (or depending on your use-case).\n\nNotice I also added a [JQL](https://support.atlassian.com/jira-service-management-cloud/docs/use-advanced-search-with-jira-query-language-jql/) to specify that this automation only executes for my JPD project / ideas - which will help narrow down the number of times this actual runs.\n" } ] } ]

[ "automation", "linked-issue", "status" ]

[ { "author": "Nick H", "body": "Hi [@Rebecca Graf](/t5/user/viewprofilepage/user-id/3020706) ,\n\nI think an automation like the one below should work for your use case:\n\n![autodelivstatus.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/346610iCF2FDFB2EFCC8279/image-size/large?v=v2&px=999 \"autodelivstatus.jpg\")\n\n1) WHEN: Issue Transitioned to (select your workflow's / idea's status)\n\n2) AND IF: Issue fields condition (select your Bucket field = Initiative)\n\n3) AND IF: Related issues condition\n\n* Related issues = Linked issues\n* Link types = implements, is Implemented by\n* Condition = Are not present\n\n4) THEN: Create issue (select your Jira project / issue type)\n\n(If you were to copy any of the JPD idea's fields to this Jira issue's fields, copy from **Current issue**)\n\n5) AND THEN: Link issues\n\n* 6) Link issues: is Implemented by - Most recently created issue\n\nI tested with the automation above after those fields / conditions were met, and it worked as expected.\n\nBut the error you shared sounds similar to what other customers have run into where the A4J (Automation for Jira) user has not been granted JPD permission.\n\nTo have this corrected, you'll want to open a ticket with JPD support so they can grant your A4J user with JPD permission. The A4J user cannot be granted permission from your end.\n\nYou can open a ticket within JPD support [HERE](https://support.atlassian.com/contact/), or under the *Give Feedback* tab \\>\\> *Get help from the support team.*\n\nA workaround for the time being is adjusting the [Actor](https://support.atlassian.com/cloud-automation/docs/what-is-a-rule-actor/) of the automation to a user that has JPD permission to see if results vary and/or are successful.\n", "comments": [ { "author": "Rebecca Graf", "body": "Great [@Nick H](/t5/user/viewprofilepage/user-id/2540930) , that worked. Step 5 was a bit different in my configuration and thus failed before. With your help I was able to fix it - thank you so much!\n\nBut: The link is only visible in Jira and not in JPD (neither as delivery ticket nor as any other linked issue). Any idea why?\n" } ] }, { "author": "Rebecca Graf", "body": "[@Nick H](/t5/user/viewprofilepage/user-id/2540930) not sure if you have seen my last comment, but I am still struggeling with one little thing:\n\nThe link is only visible in Jira and not in JPD (neither as delivery ticket nor as any other linked issue).\n\nAny idea why?\n", "comments": [ { "author": "Nick H", "body": "Hi [@Rebecca Graf](/t5/user/viewprofilepage/user-id/3020706) ,\n\nPlease share a screenshot of your configured automation. The JPD idea should link to the Jira delivery as \"Implements,\" and the delivery should then be found in the idea's Delivery tab.\n\nHere are screenshots of the same automation previously shared, along with a test run just before this response:\n\n![del1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/347092i53770C02AB19E3E0/image-size/large?v=v2&px=999 \"del1.jpg\")![del2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/347094iDCC06716FBF33F9A/image-size/large?v=v2&px=999 \"del2.jpg\")![del3.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/347095i7CFA67B1D4BC8753/image-size/large?v=v2&px=999 \"del3.jpg\")![del4.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/347093iD6392BB3755C2B19/image-size/large?v=v2&px=999 \"del4.jpg\")\n\nFeel free to also open a JPD support ticket [HERE](https://support.atlassian.com/contact/#/), or within JPD under the *Give Feedback* tab \\>\\> *Get help from the support team*.\n" }, { "author": "Rebecca Graf", "body": "Thanks once again for your help [@Nick H](/t5/user/viewprofilepage/user-id/2540930) ! I just mixed up is implemented by and implements, after changing the config it works now!\n" } ] } ]

[ "automation", "delivery", "issue-link", "jira" ]

[ { "author": "Tanguy Crusson", "body": "Hi [@Wendy Grapentine](/t5/user/viewprofilepage/user-id/5294147) , unfortunately you can't get it back (that's why we show that big scary warning asking you to type the field name before confirming). You'll have to re-create it...\n\nIf you look in the \"history\" tab for each idea, you can find which value it had for that field.\n", "comments": [ { "author": "Wendy Grapentine", "body": "Thank you\n" } ] }, { "author": "Dirk Lachowski", "body": "Isn't that just a single select tag field?\n", "comments": null } ]

[ { "author": "Nick H", "body": "Hi [@Wendy Grapentine](/t5/user/viewprofilepage/user-id/5294147) ,\n\nJPD and Confluence don't necessarily have a prebuilt integration, but we see some customers pasting a view's link into a Confluence page to populate a preview!\n\nFor more on this in general: [Improvements to Atlassian links](https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Improvements-to-Atlassian-links/ba-p/2598564)\n\nChanges cannot be made in Confluence to reflect back in JPD, but any changes completed to the view within JPD should reflect in Confluence:\n\n![confl1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/346417i2A40EAA2A768105B/image-size/large?v=v2&px=999 \"confl1.jpg\")![confl2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/346416i07E2073B44808479/image-size/large?v=v2&px=999 \"confl2.jpg\")\n", "comments": null }, { "author": "Amanda Barber", "body": "If you drop the link for your view into Confluence, the view will be displayed. I recorded a quick Loom to show it here: <https://www.loom.com/share/6abad4973a5a4a32a56c3cb2e252c16e>\n", "comments": [ { "author": "Wendy Grapentine", "body": "Thank you\n" } ] } ]

[ "confluence", "jira-product-discovery" ]

[ { "author": "Walter Buggenhout", "body": "Hi [@Seth Mason](/t5/user/viewprofilepage/user-id/5404484),\n\nNo. The *about this view* is a link to the dialog that pops up on the right hand side explaining what it is about.\n\nYou have probably noticed that you can put quite an extensive description / manual in that box, as a view can contain a lot of information that you might want to explain to your users. As it can become quite elaborate, plenty of space has been provided rather than having a short popup or something.\n\nThe *about this view* text is about the only thing that is not customisable.\n\nHope this helps!\n", "comments": null } ]

[ { "author": "John Funk", "body": "Hi Andrew - Welcome to the Atlassian Community!\n\nYou do have a license for the Jira Project Discovery product - correct?\n", "comments": null } ]

[ "cloud", "jira", "jira-cloud" ]

[ { "author": "Hermance NDounga", "body": "Hello Omar,\n\nThank you for raising this bug, we are investaging it.\n\nCheers,\n\nHermance\n", "comments": null }, { "author": "Amina Bouabdallah", "body": "hi! any chance you might share a screenshot to the problem you faced? is it still happening?\n", "comments": null } ]

[ { "author": "Tanguy Crusson", "body": "Hi Mark, we don't currently have those on the roadmap. What are you trying to do?\n", "comments": [ { "author": "Mark Sadegursky", "body": "We have global fields that we would like to add to JPD that track certain values that would be tied to the delivery tickets, being able to leverage those custom fields that have been built is critical to the success of using JPD. This also goes into roadmap reporting and being able to create the necessary pages automatically for presentations using the board views.\n" } ] } ]

[ { "author": "Amina Bouabdallah", "body": "Hi Mark! when you say \"dependency\" do you mean dependency on teams (team X needs work from team y), or dependency on idea (for Idea X to ship, we first need to ship Idea A).\n\nFor the latter you can leverage issue links. From an idea's issue view, you can link to another idea in the project. Then once on an idea, you can read what dependent ideas a given idea has. You have multiple issue link types, to denote how 2 ideas are linked.\n\nHope this helps!\n\nAmina\n", "comments": null } ]

[ { "author": "Stepan Kholodov _Tempo_", "body": "Hello [@?krlantov? Nikola](/t5/user/viewprofilepage/user-id/5585020) \n\nThe goal with the JQL approach is to exclude issues from the top level of the structure, that will later be duplicated by an Extend generator. So you can try to add to your current JQL query of the Insert generator a condition like this: ... *AND parent is empty* \nThis way the inserter will not add issues of Epics even if they match other conditions; but these issues will be added by the extender if their parent Epic is present in the structure. \n\nI hope this helps. If you need further assistance or if you have other questions about Structure - please reach out to us directly at our [support portal](https://tempo-io.atlassian.net/servicedesk/customer/portal/6/group/1051). The email address you mentioned indeed no longer in use, so please use the link. \n\nBest regards, \nStepan \nTempo (the Structure app vendor)\n", "comments": [ { "author": "?krlantov? Nikola", "body": "Hello [@Stepan Kholodov _Tempo_](/t5/user/viewprofilepage/user-id/5205346) ,\n\nthank you very much, that makes perfect sense, but unfortunately this condition does not work for me, because in my case the parent is never empty. Epic is linked to an initiative owned by someone else and I don't need to see it in my structure. So I can't use *\"and parent is empty\"*.\n\nIs there another way to not display duplicates using JQL? I really appreciate your help.\n\nBest regards\n\nNikola\n" } ] } ]

[ { "author": "Amina Bouabdallah", "body": "hey there! we don't have the ability to group by X then Y yet. I can add this request to our insights for future prioritization!\n", "comments": null } ]

[ "field", "group", "swimlane", "timeline" ]

[ { "author": "Jennifer Leitch", "body": "I'm not sure if this would work for you, but for us, we use various alert emails to OpsGenie to send the alert. For the integration, I edit the Alert Rule to prepend the system name, and then have then have the dynamic properties subject. This tells us what system it is (very helpful for the middle of the night alerts!) \n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/344062iAF3431992A774B49/image-size/large?v=v2&px=999 \"image.png\")\n", "comments": [ { "author": "Bob Dobson", "body": "I ended up finding something almost identical under the integration we had set up. Thanks! Great minds really do think along the same lines.\n" } ] } ]

[ "cloud", "opsgenie-cloud" ]

[ { "author": "Shashwat Khare", "body": "Hello [@Cameron McAuley](/t5/user/viewprofilepage/user-id/1913734) , \n\nThis is Shashwat from Opsgenie support and here to help! :) \n\nYes, you can use the _payload operator to bring in the entire JSON payload into the Opsgenie alert description field. \n\nFor extracting exact variable values like env out of the above JSON, we would recommend using one of the string operators from the below help document from substringBetween, substring(int from), substring(int from, int to) OR extract(regular expression): \n<https://support.atlassian.com/opsgenie/docs/string-processing-methods-in-opsgenie-integrations/> \n\nBest, \nShashwat\n", "comments": null } ]

[ "cloud", "opsgenie-cloud" ]

[ { "author": "Shashwat Khare", "body": "Hello [@Jacob Clark](/t5/user/viewprofilepage/user-id/5575246) , \n\nThis is Shashwat from Opsgenie support and here to help! :) \n\nCould you please help confirm if you're passing these URLs in the Alert message or description field in the Opsgenie alert? \n\nThis is because the alert message is limited up to 130 characters whereas the alert description field has a big limit of up to 15000 characters: \n\n![Screenshot 2024-08-26 at 4.30.05?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/343807i501B9BBE61EBF738/image-size/large?v=v2&px=999 \"Screenshot 2024-08-26 at 4.30.05?PM.png\") \n\n<br />\n\nBest, \nShashwat\n", "comments": [ { "author": "Jacob Clark", "body": "Thank you, Shashwat, this addresses my concern!\n" }, { "author": "Shashwat Khare", "body": "My pleasure, Jacob, glad it helped! :)\n" } ] } ]

[ "cloud", "opsgenie-cloud" ]

[ { "author": "Wei Wung", "body": "Hi [@Alex John](/t5/user/viewprofilepage/user-id/5081011)\n\nThank you for reaching out! Currently, the initial incoming alert gets associated with the incident that is being created. The incident generates a responder alert for each of the incident responders. If the incident was manually created, an additional responder alert is generated for the person that created the incident.\n\nUnfortunately, at this time, when the incident generated responder alert is acknowledged, it doesn't ack the incoming (associated) alert(s). This is probably because sometimes there can be multiple incident responders and if so, the incident will generate multiple responder alerts to separately notify these responders, each following their own escalation paths.\n\nWe have a similar feature request: ([OPSGENIE-28](https://jira.atlassian.com/browse/OPSGENIE-28)) Auto-close associated alerts when an incident is closed and acknowledge when incident is resolved\n\nFrom within the incident, under \"**Associated Alerts** \", when you click on \"**See alerts** \", you have the option to selectively **Close** associated alerts or \"Close all\" of them, although there isn't an \"Ack\" option. \n\nHope the above helps!\n\nBest Regards,\n\nWei\n", "comments": [ { "author": "Alex John", "body": "Thank you for the information, Wei!\n" } ] } ]

[ { "author": "Wei Wung", "body": "Hi [@gnaneswar seshu](/t5/user/viewprofilepage/user-id/5574205)\n\nThank you for reaching out!\n\nPlease try using this format:\n\n```\ncreatedAt>=\"20-08-2024T10:30:00Z\" and createdAt<=\"22-08-2024T18:30:00Z\"\n```\n\nThe workaround in the following ticket addressed this issue as well:\n\n<https://jira.atlassian.com/browse/OPSGENIE-1588> Incident API and Alert API using the \"createdAt\" condition display incorrect usage error\n", "comments": null } ]

[ { "author": "Muhammad Zeeshan", "body": "Hey [@Sanjana Nellore](/t5/user/viewprofilepage/user-id/5574203)\n\nIt may not be outright possible in Opsgenie to create an alert when you have 100 Emails received in 30 minutes, which is why we have a Feature suggestion ticket for such functionality here: <https://jira.atlassian.com/browse/OPSGENIE-471> that you can track and vote on.\n\nHowever, as a workaround you can make use of [Notification policies](https://support.atlassian.com/opsgenie/docs/create-and-manage-team-alert-policies/#Notification-Policy) which can delay / suppress notifications until a certain deduplication count is met in a certain period for an alert but will not notify initially when the alert is created.\n\nIn order to make use of that you will need to make sure that all those alerts created via the Email integration are deduplicated so that they can be counted together as a single alert and their deduplication count used to trigger the notification policy:\n\n![Screenshot 2024-08-23 at 15.21.59.png](https://community.atlassian.com/t5/image/serverpage/image-id/343483i3719F48082B22D3A/image-size/large?v=v2&px=999 \"Screenshot 2024-08-23 at 15.21.59.png\")\n\nBR,\n", "comments": null } ]

[ "cloud", "opsgenie-cloud" ]

[ { "author": "Elelta D", "body": "Hey there Jonathan,\n\nThanks for posting here with an interesting problem, as you state the Get Schedule api does not give you the time a person was on call.\n\nThe analytics with Opsgenie would have this information in the format you need it, it is possible to schedule an export of this data in a CSV format to be delivered to on of the Opsgenie users.\n\nHere is an outline of how to do that.\n\n<https://community.atlassian.com/t5/Opsgenie-articles/Creating-a-Scheduled-Report-in-Opsgenie-Explanation-of/ba-p/2720680>\n\nwould this wokr for you?\n", "comments": null } ]

[ { "author": "Mona Singh", "body": "Hi [@Kaloyan G_ Georgiev](/t5/user/viewprofilepage/user-id/5513724) ,\n\nThis is Mona here, happy to help :)\n\nUnfortunately, we will not be able to recover a deleted team in Opsgenie directly from the UI. You'll have to recreate the team and configuration in it according to the data in the logs. \n\nIf the team was deleted within the last 13 days, you can check the Logs in your account under Settings and search for **\"Team \\[TEAM NAME\\] deleted\" or \"Team\" AND \"deleted\".** Once you have the data, you can perform the restoration manually by adding the Team in the UI and configuring it as per the logs retrieved.\n\nThe other way would be to create Team, Routing, Escalation, Schedule \\& Rotations using the API Endpoints. \n\n[Create Team](https://docs.opsgenie.com/docs/team-api#section-create-team) \n[Create Schedules](https://docs.opsgenie.com/docs/schedule-api#section-create-schedule) \n[Create Escalations](https://docs.opsgenie.com/docs/escalation-api#section-create-escalation) \n[Create Routing Rules](https://docs.opsgenie.com/docs/team-routing-rule-api#section-create-team-routing-rule) \n[Create Integration](https://docs.opsgenie.com/docs/integration-api#section-create-api-based-integration)\n\nPlease let me know if this works for you. Incase you have any further queries, please feel free to reach out to us by creating a ticket in this [link](https://support.atlassian.com/) and we'll take it from there :) \n\nThanks! \nMona\n", "comments": [ { "author": "Kaloyan G_ Georgiev", "body": "Thank you, Mona! Appreciate the response!\n" } ] } ]

[ "cloud", "opsgenie-cloud" ]

[ { "author": "Rafael Meira", "body": "Hey [@Dominic Utz](/t5/user/viewprofilepage/user-id/5571380) \n\nCan you check these steps to [map priority](https://support.atlassian.com/opsgenie/docs/what-is-the-priority-level-of-integration/) from Statuspage to Opsgenie? \n\n**Check Integration Settings** for additional field mapping. \n**Use Tags/Custom Fields** to set priorities via [Opsgenie rules.](https://support.atlassian.com/opsgenie/docs/add-a-forwarding-rule/) \n[**Create Policies**](https://support.atlassian.com/opsgenie/docs/create-and-manage-maintenance-policies/) to adjust priorities based on alert conditions. \n**Use Opsgenie's [API](https://docs.opsgenie.com/docs/api-overview)** to update priorities programmatically. \n\nIf these steps don't resolve the issue, please open a support ticket at [Atlassian Support](https://support.atlassian.com/contact/). so our team could assist and troubleshoort it. \n\n<https://support.atlassian.com/opsgenie/docs/integrate-opsgenie-with-statuspage/>\n", "comments": null } ]

[ "datadog", "statuspage" ]

[ { "author": "Tejaswi G", "body": "Hi [@Ronald Heijn Buys](/t5/user/viewprofilepage/user-id/5562003)\n\nThis is Tejaswi from the Atlassian support team and happy to help.\n\nIf you are using the Atlassian login and wish to login to Opsgenie with Azure AD via SSO. You need to use the Atlassian Access (Atlassian Guard) to setup this. Ideally, You should not be billed for the users using only the Opsgenie for the SSO.\n\nYou can refer to Guard page [here](https://support.atlassian.com/subscriptions-and-billing/docs/manage-your-bill-for-atlassian-guard-standard/) for more details on this.\n\nKind Regards, \nTejaswi\n", "comments": null } ]

[ "cloud", "opsgenie-cloud" ]

[ { "author": "Sean Suwal", "body": "Hey [@HN,](https://community.atlassian.com/t5/user/viewprofilepage/user-id/5535606)\n\nThank you for reaching out to Atlassian Community!\n\nYes, this can be achieved via the use of [Regular expressions for customizing and filtering alerts](https://support.atlassian.com/opsgenie/docs/regular-expressions-for-improved-alert-filtering/)\n\nTo use the **OR** condition for an entry you can use the **Matches (Regex)** and then have the values as **.\\***(Value1\\|Value2\\|Value3).\\*\n\nNote: The rules are executed in a top-down hierarchy, which means if the first rule matches, it will skip the remaining rules.\n\nHere's an example screenshot of one of the conditions:\n\n![Screenshot 2024-08-16 at 1.08.00?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/342365i16EB3D80B9527C63/image-size/large?v=v2&px=999 \"Screenshot 2024-08-16 at 1.08.00?PM.png\")\n\nI hope this helps resolve your query.\n\nRegards, \nSean\n", "comments": [ { "author": "HN", "body": "That's awesome and helps immensely [@Sean Suwal](/t5/user/viewprofilepage/user-id/5078924)!\n\nI don't have permissions to view the screenshot unfortunately.\n\nOne more question in addition to the top-down hierarchy. How would you go about having multiple groups getting alerts?\n\nIdeally my situation needs to have cascading alerts, so if Priority is greater than 4, then the rule for greater than 3 would need to be addressed as well as two different teams are on call.\n\n<br />\n\nI've considered having escalation policies for the different teams, having the users for lower priority included in the higher priority escalation but this seemed a bit messy. I'm still learning how to utilize OpsGenie effectively, so I'm eager to know if there's better ways to do things.\n" }, { "author": "Sean Suwal", "body": "Hi [@HN](/t5/user/viewprofilepage/user-id/5535606)\n\nI am glad it was helpful. I have also updated the screenshot, which you should now be able to see.\n\nBased on your requirements, I believe using [**Global alert policies**](https://support.atlassian.com/opsgenie/docs/create-and-manage-global-alert-policies/) would be best suited. With the global policy, you can set your condition which when matched, adds the team(s) you want as responders.\n\nLet us know how you go.\n\nRegards, \nSean\n" } ] } ]

[ { "author": "Alicia Peebles", "body": "Hi [@Dario Alarc?n](/t5/user/viewprofilepage/user-id/5307057) !\n\nYou can setup Opsgenie alerts from JSM requests! You will need to integrate your JSM with Opsgenie but once that is done, then you can set alerts based on many different components.\n\nHere is some documentation for you to refer to: [Integrate Opsgenie with Jira Service Management Cloud \\| Opsgenie \\| Atlassian Support](https://support.atlassian.com/opsgenie/docs/integrate-opsgenie-with-jira-service-management-cloud/)\n\nI am not sure if the recent merger of Opsgenie into the JSM platform changes this process, as I have not completed that.\n\nHope that helps! Have an awesome week!\n", "comments": [ { "author": "Dario Alarc?n", "body": "Hi [@Alicia Peebles](/t5/user/viewprofilepage/user-id/5415758)\n\nThanks for you reply. Actually I?m using Opsgenie with Jira **Service Management's****Standard** **plan**, that to say, with the merged version.\n\nI followed the steps from the documentation but didn't find the JSM Cloud integration in the search. \nI would like to know if that is possible to enable in my JSM projects? \nI have different request types to configure alerts in Opsgenie. \nCommunity, I will keep atent to you comments.\n" } ] }, { "author": "Alicia Peebles", "body": "Hi [@Dario Alarc?n](/t5/user/viewprofilepage/user-id/5307057)\n\nThere is a clarification in the documentation for the Standard plan, Integrations are not in the Settings on the Standard plans. It does say you can add to a dashboard, however, this is only for 1 team. That could make setting the alerts a bit more difficult, if you are trying to do it for multiple teams.\n\n![2024-08-15_08-59-45.png](https://community.atlassian.com/t5/image/serverpage/image-id/341981i5D0AECFB6782E8B7/image-size/large?v=v2&px=999 \"2024-08-15_08-59-45.png\")\n", "comments": null } ]

[ "alert", "jira-service-management", "monitoring" ]

[ { "author": "Maryam Gharib", "body": "Hi Alan, \nThanks for getting back to me. ? \nIs it because I don't have admin settings I can't see the logs from the Settings?\n\n**Settings** {#toc-hId--349617843}\n----------------------------------\n\n**My Profile** \n[Profile](https://id.atlassian.com/manage-profile) \n[Profile settings](https://onthebeach.app.opsgenie.com/settings/user/profile) \n[Notifications](https://onthebeach.app.opsgenie.com/settings/user/notification) \n[Your on-call schedule](https://onthebeach.app.opsgenie.com/settings/user/onCallSchedule) \n[Forwarding rules](https://onthebeach.app.opsgenie.com/settings/user/forwardingRules) \n**Integrations** \n[Heartbeats](https://onthebeach.app.opsgenie.com/settings/heartbeat) \n**Incident Config** \n[Conference rooms](https://onthebeach.app.opsgenie.com/settings/conferences) \n[Incident templates](https://onthebeach.app.opsgenie.com/settings/incident-templates) \n[Response roles](https://onthebeach.app.opsgenie.com/settings/response-roles) \n[Email templates](https://onthebeach.app.opsgenie.com/settings/email-templates) \nThanks again \nMaryam\n", "comments": null }, { "author": "Alan Violada", "body": "Hey Maryam, Alan from the Opsgenie Support Team here.\n\nFrom your description, it seems that you might be using the Heartbeat feature and using emails to maintain the heartbeat. Correct me if I'm wrong!\n\nTo validate what is being received, your best bet would be using the logs in the \"**Settings -\\> Logs**\" tab. That should show you everything coming in and out of the Opsgenie instance, and all actions taken.\n\nYou can also use search queries to filter this down, related documentation:\n\n[Search logs](https://support.atlassian.com/opsgenie/docs/search-logs/)\n\nAlso some documentation on the Heartbeats functionality:\n\n[Heartbeats documentation](https://support.atlassian.com/opsgenie/docs/add-heartbeats-to-monitor-external-systems/)\n\nIf you need more detailed assistance, feel free to create a ticket at [Atlassian Support](https://support.atlassian.com) and we will be happy to help troubleshoot!\n\nRegards,\n\nAlan\n", "comments": null } ]

[ "cloud" ]

[ { "author": "Rafael Meira", "body": "Hey [@Eric Leo Lidi Okala](/t5/user/viewprofilepage/user-id/5568088) \n\nTo further investigate, since ti is a integration issue and we would need to request access permission to your account, I would recommend you to create a ticket with out support here: \n\n<https://support.atlassian.com/contact/#/> \n\n<br />\n\nBest, \nRafa\n", "comments": [ { "author": "Eric Leo Lidi Okala", "body": "Hi Rafael,\n\nAppreciate the update, I will request account admin to request support ticket on behalf my department.\n\nRegards,\n\nEric\n" }, { "author": "Rafael Meira", "body": "[@Eric Leo Lidi Okala](/t5/user/viewprofilepage/user-id/5568088) Your welcome :)\n" } ] } ]

[ "jira-helpdesk", "zabbix" ]

[ { "author": "Elelta D", "body": "Hey there Emily,\n\nWelcome to the community :-)\n\nI see you would like to export your rotations but you cannot see the two teams that you work in, are you able to navigate to Teams and see the rotation from that screen? If you are a member of a team you should be able to see the on-call schedule.\n\nThat all said, it is not possible to download JUST your own schedule, you get the whole team's schedule.\n\nIf you goal is to get notified of you upcoming rotation, I recommend setting up your [notification rules.](https://support.atlassian.com/opsgenie/docs/create-and-manage-notification-preferences/#:~:text=Schedule%20Start%2C%20etc).-,Notification%20Rules,-Watch%20Using%20notification) You can, for example, you can configure it so you get an email or a text a few days before your scheduled shift, you have the option to get notified about the start and the end of your schedule.\n\n* **Schedule Start:** Your on-call rotation is being started.\n\n* **Schedule End:**Your on-call rotation is being ended.\n\nI hope this help, please do let me know if you have further questions :)\n\nCheers\n\nElelta\n", "comments": null } ]

[ { "author": "Slifer", "body": "Yes, Opsgenie can track events from Salesforce Service Cloud and create tickets in Jira, along with supporting various other integrations. Here's an overview of how it works:\n\n#### 1. Salesforce Service Cloud Integration: {#toc-hId-351332475}\n\n- Event Monitoring: Opsgenie can be connected with Salesforce Service Cloud to monitor specific events like case creation, status updates, or other defined triggers. \n- Custom Workflows: You can configure custom workflows in Salesforce to send notifications or trigger API calls to Opsgenie when certain events occur.\n\n#### 2. Generating Alerts in Opsgenie {#toc-hId--1456121988}\n\n- Once integrated, Opsgenie can receive these events as alerts. \n- These alerts can include detailed information from Salesforce, such as the case number, description, and priority level.\n\n#### 3. Initiating Actions (e.g., Creating Jira Tickets) {#toc-hId-1031390845}\n\n- Jira Integration: Opsgenie seamlessly integrates with Jira, enabling it to automatically create issues or tickets in Jira based on the alerts it processes. \n- Automation Rules: You can set up automation rules in Opsgenie to define when and how these tickets are created in Jira. For instance, if a high-priority case is logged in Salesforce, an alert can trigger the creation of a corresponding high-priority ticket in Jira.\n\n#### 4. Bidirectional Synchronization: {#toc-hId--776063618}\n\n- In some configurations, Opsgenie can keep the Jira ticket updated with changes from Salesforce and vice versa, ensuring both systems remain synchronized.\n\n#### 5. Escalations and Notifications: {#toc-hId-1711449215}\n\n- Opsgenie can escalate issues, notify the appropriate teams, and perform additional actions based on the alert status or responses from Jira.\n\n#### 6. Setting Up the Integration: {#toc-hId--96005248}\n\n<https://support.atlassian.com/opsgenie/docs/integrate-opsgenie-with-salesforce-service-cloud/>\n", "comments": null } ]

[ { "author": "Sean Suwal", "body": "Hi Kaloyan,\n\nThank you for contacting the Atlassian Community!\n\nCurrently, we don't have the ability to import/ list public holidays into Opsgenie. However, we do have a feature request [OPSGENIE-781](https://jira.atlassian.com/browse/OPSGENIE-781) open. Please vote and add yourself as a watcher to be notified of any updates.\n\nIn saying that, the workaround for you would be to create a [maintenance policy](https://support.atlassian.com/opsgenie/docs/create-and-manage-maintenance-policies/) for the public holiday that then disables/ enables the notification policy you have in place.\n\nI hope this helps.\n\nRegards, \nSean\n", "comments": null } ]

[ "cloud", "opsgenie-cloud" ]

[ { "author": "Chris DeGidio", "body": "Hi [@Edgardo Isaula](/t5/user/viewprofilepage/user-id/5566653)\n\nYou would set this up in the team escalation policy. There are two options to select during a notification step/event. If the alert is not closed or if the alert is not ackd. You will want to add a step for not closed:\n\n![2024-08-13_13-57-21.png](https://community.atlassian.com/t5/image/serverpage/image-id/341578i94FDB97684EBF37D/image-size/large?v=v2&px=999 \"2024-08-13_13-57-21.png\")\n", "comments": [ { "author": "Edgardo Isaula", "body": "Hello [@Chris DeGidio](https://community.atlassian.com/t5/user/viewprofilepage/user-id/3202394) ! thank you for your answer! However, I saw that option, but the problem with it, is that it applies it to all of the alerts (P1-P5), it does not let me customize it by priority, for example, if I want to notify x user if a P1 alert is acked but not closed in 120 min, and another one, I want to notify x user if a P2 alert is acked but not closed in 180 min, so we can meet SLAs especifically. \n\nThanks in advance.\n" }, { "author": "Chris DeGidio", "body": "hi [@Edgardo Isaula](/t5/user/viewprofilepage/user-id/5566653) you would apply a different escalation policy dependent on the details of the alert via a routing rule. So for example for a p1 you can route that alert to its own escalation policy seperate from other alerts with different priorities.\n\n![2024-08-14_08-19-28.png](https://community.atlassian.com/t5/image/serverpage/image-id/341743iE6D96E99DA8EC9D7/image-size/large?v=v2&px=999 \"2024-08-14_08-19-28.png\")\n" }, { "author": "Edgardo Isaula", "body": "Thank you [@Chris DeGidio](/t5/user/viewprofilepage/user-id/3202394) that worked great :)\n" } ] }, { "author": "Edgardo Isaula", "body": ".\n", "comments": null } ]

[ "cloud", "jira-service-management" ]

[ { "author": "Mubeen Mohammed", "body": "Hello [@Fabio Santos](/t5/user/viewprofilepage/user-id/5531864)\n\nThank you for contacting the Atlassian Community!\n\nOpsgenie offers robust event management features, making it a strong choice compared to other observability platforms.\n\n1. **Alerting and Notification:** Advanced alerting with customizable policies and multiple notification methods.\n\n2. **Incident Management:** Seamless incident creation and tracking, with strong integration with tools like Jira.\n\n3. **Integrations:** Extensive integrations with monitoring and collaboration tools for enhanced workflows.\n\n4. **Event Correlation:** Effective alert correlation and deduplication to reduce noise.\n\n5. **On-Call Management:** User-friendly on-call scheduling with automated escalation policies.\n\n6. **Reporting and Analytics:** Detailed insights into incident trends and operational performance.\n\nTo explore Opsgenie's full capabilities, you can start a trial at [this link](https://www.atlassian.com/software/opsgenie/try).\n\nI hope the details provided are helpful.\n\nRegards\n\nMubeen Mohammed\n\nCloud Support Engineer\n", "comments": null } ]

[ "observability" ]

[ { "author": "Mubeen Mohammed", "body": "Hello [@Fabio Santos](/t5/user/viewprofilepage/user-id/5531864)\n\nThank you for contacting the Atlassian Community!\n\nPlease note that currently, the AIOps feature is available within Jira Service Management and is designed to enhance its incident management processes.\n\nAs for Opsgenie, while similar functionalities are part of its robust alert management and incident response features however, this particular AIOps capability isn't available in Opsgenie at this time.\n\nOpsgenie continuously evolves, and new integrations and features are regularly considered to improve its offerings. You can follow <https://www.atlassian.com/roadmap/cloud?selectedProduct=opsgenie> for Opsgenie product roadmap.\n\nI hope this is helpful.\n\nRegards\n\nMubeen Mohammed\n\nCloud Support Engineer\n", "comments": null } ]

[ "aiops" ]

[ { "author": "Bruna Silva", "body": "Hello [@Jason Rogers](/t5/user/viewprofilepage/user-id/5508518),\n\nThank you for reaching out to Atlassian Community!\n\nWhen using a [site-level integration](https://support.atlassian.com/jira-service-management-cloud/docs/add-an-integration-site-level/), it is possible to set more than 1 Team in the **Responders** field in its **Create alert** rule:\n\n![Community.png](https://community.atlassian.com/t5/image/serverpage/image-id/341343iC1C704AD64303B8F/image-dimensions/389x228?v=v2 \"Community.png\")\n\nHowever, if you configured a [team-level integration](https://support.atlassian.com/jira-service-management-cloud/docs/add-an-integration-team-level/), the **Responders** will always be the Team you used to add that integration.\n\nPlease note that *site-level integrations* are only available on Jira Service Management Premium and Enterprise plans.\n\nIf you have any other questions regarding this matter, please let us know.\n", "comments": [ { "author": "Jason Rogers", "body": "Great. Thanks for this.\n\nI had indeed set up Team level Syncs, but can recreate the ones where I need two or more Teams.\n\nThanks!\n\nJ\n" } ] } ]

[ "alerts", "jsm", "opsgenie-cloud", "teams" ]

[ { "author": "Sean Suwal", "body": "Hi Amardeep,\n\nThank you for reaching out to the Atlassian Community!\n\nRegarding your query, if the field application name is being sent in the payload received by Opsgenie, you should be able to extract the custom field into the alert by following the steps outlined in our community article [How to Extract Custom Fields and Data into an Alert](https://community.atlassian.com/t5/Opsgenie-articles/How-to-Extract-Custom-Fields-and-Data-into-an-Alert/ba-p/2133902)\n\nI hope this helps.\n\nRegards, \nSean\n", "comments": null } ]

[ "cloud", "opsgenie-cloud" ]

[ { "author": "Mubeen Mohammed", "body": "Hello [@Lubom?r Kostal](/t5/user/viewprofilepage/user-id/5562635)\n\nThank you for contacting the Atlassian Community!\n\nWhen sending alerts from Kibana to Opsgenie using a webhook, you'll need to ensure that your payload is correctly formatted to include the tags. The Opsgenie API expects a specific JSON structure, and if the tags are not appearing, it's likely due to a formatting issue in the payload you're sending.\n\n{ \"message\": \"Sample Alert\", \"description\": \"This is a sample alert description\", \"priority\": \"P3\", \"tags\": \\[\"tag1\", \"tag2\", \"tag3\"\\], \"details\": { \"key1\": \"value1\", \"key2\": \"value2\" } }\n\nFrom the above payload you shared it looks like you need to include \n\"tags\": {{#context.tags}}\\[\"{{.}}\"\\]{{/context.tags}}\n\nI hope the details provided are helpful.\n\nRegards\n\nMubeen Mohammed\n\nCloud Support Engineer\n", "comments": null } ]

[ "cloud", "devops" ]

[ { "author": "Bhanu", "body": "Hi [@Calvin](/t5/user/viewprofilepage/user-id/4851947)\n\nLegacy automation and jira automation should help you build alerts for your use case.\n", "comments": null } ]

[ { "author": "Shashank Kumar", "body": "Hello Piotr,\n\nWelcome to Atlassian community.\n\nYou can see an example at [How to perform a Git SSH checkout from a Bamboo Script Task](https://confluence.atlassian.com/bamkb/how-to-perform-a-git-ssh-checkout-from-a-bamboo-script-task-741999875.html) where there is a similar scenarion of what you are trying to achieve.\n\nLet me know if this helps.\n\nRegards,\n\nShashank kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n", "comments": [ { "author": "Piotr Wilk-Juraszek", "body": "Hello.\n\nThank you for your answer. I have seen this solution, but it seems to not work with something that I am trying to achieve.\n\nI have tried something like this but it is not working:\n\n GIT_SSH_COMMAND='ssh -i /Path/to/file -o IdentitiesOnly=yes' python -m pip install -r .\\requirements.txt\n\nI need those repos to be installed in venv by **pip** in order to execute code that needs them. Pip is using **git** to clone repository, and then it is installing it to venv.\n\nKey specified in `/Path/to/file` is added to bitbucket repositories.\n" } ] } ]

[ "python", "ssh" ]

[ { "author": "Eduardo Alvarenga", "body": "Good day, **Phil**,\n\nThank you for pointing that out. The Bamboo docker images and many other Atlassian products all depend on [Eclipse Temurin images](https://hub.docker.com/_/eclipse-temurin/) as a base image. Temurin images [have been refactored to ship with Ubuntu 24.04](https://github.com/adoptium/containers/pull/534/files), so our images followed that version.\n\nWe are working internally to pin our images to **Noble**, so future releases will not be affected by that change in the base image.\n\nIf you'd like to continue working with the **Jammy** version, pull the Docker image by its digest, as you have already identified. That will help you recover from your latest stable point, but it will also tie you to a specific version of the image, which will not receive any updates. Hence, we recommend you adjust your build process to adapt to the new **Noble** version.\n\nYou can also build your own image from scratch by cloning the [project](https://bitbucket.org/atlassian-docker/docker-bamboo-agent-base/src/master/). Customised images are not supported so you will have to read through the code and understand the process.\n\nCheers,\n\nEduardo Alvarenga \nAtlassian Support APAC\n\n**--please don't forget to Accept the answer if the reply is helpful--**\n", "comments": [ { "author": "Eduardo Alvarenga", "body": "Hey [@Phill Pafford](/t5/user/viewprofilepage/user-id/704705),\n\nGood news!\n\nWe released **jdk11-jammy** and **jdk17-jammy** docker tags for the [Bamboo Agent Base docker image](https://hub.docker.com/r/atlassian/bamboo-agent-base).\n\nThat should help you with the earlier Ubuntu 22.04 version. Those *jammy* tags are one-offs, meaning they will not receive further updates, and you must plan your upgrade to the latest tags, **jdk11** or **jdk17,** that run on Ubuntu 24.04 (noble).\n\nRegards,\n\nEduardo Alvarenga \nAtlassian Support APAC\n\n**--please don't forget to Accept the answer if the reply is helpful--**\n" }, { "author": "Phill Pafford", "body": "HI [@Eduardo Alvarenga](/t5/user/viewprofilepage/user-id/4365410) thanks for the explanation but for a released version you should not go back and update them with the same SEMVER, especially if there is a breaking change.\n\nThank you for the work around but this is disappointing as a consumer of Atlassian products.\n\n<https://semver.org/>\n\nNOTE: this also breaks what is documented\n\n<https://confluence.atlassian.com/bamkb/how-to-upgrade-the-java-version-used-by-bamboo-1252329397.html>\n\nBamboo 9.2 is the LTS as well:\n\n<https://confluence.atlassian.com/bambooreleases/bamboo-9-2-lts-change-log-1189803706.html>\n\nSo I'm not understanding how this is supported if you keep breaking backward capabilities\n" }, { "author": "Eduardo Alvarenga", "body": "Hello [@Phill Pafford](/t5/user/viewprofilepage/user-id/704705)\n\nThank you for your concern. The version of Bamboo SEMVER has not changed. The Atlassian software remains the same as before. What changed was the Digest used by the base image, which is related to the docker tag and not a specific version. Due to an update in the Temurin Docker base image, our image ended up using that version once it was rebuilt.\n\nWe apologize for this, as it was beyond our control. To prevent this from happening again in the future if Temurin decides to update its base OS version, our images are now pinned to the Noble tag.\n\nKind regards,\n\nEduardo Alvarenga \nAtlassian Support APAC\n\n**--please don't forget to Accept the answer if the reply is helpful--**\n" } ] }, { "author": "Yevhen", "body": "[@Phill Pafford](/t5/user/viewprofilepage/user-id/704705) neither product binaries nor Java version have changed. The underlying OS and packages (especially packages) can change. We regularly rebuild and push images to get patched packages from Ubuntu repositories to mitigate CVEs. May I inquire about your use case? How exactly updating Ubuntu version impacted you?\n\nLike [@Eduardo Alvarenga](/t5/user/viewprofilepage/user-id/4365410) said, we'll be pinning base image tag to both jdk and ubuntu version (previously it was just jdk).\n", "comments": [ { "author": "Phill Pafford", "body": "we use the base image and extend it to add additional capabilities, some of the install process relies on specific packages at the OS level, since the OS was updated, the packages are not compatible.\n\nI was not expecting the OS version to change in a tagged base image\n" } ] } ]

[ "bamboo-server", "server" ]

[ { "author": "Shashank Kumar", "body": "Hello [???](https://community.atlassian.com/t5/user/viewprofilepage/user-id/5545873),\n\nWelcome to Atlassian community.\n\nBamboo project and plan variables are independent of any agents, can you try to explain me your scenario properly, what exactly you are trying to achieve ?\n\nRegards,\n\nShashank Kumar\n", "comments": [ { "author": "???", "body": "thanks to your reply, [@Shashank Kumar](/t5/user/viewprofilepage/user-id/4693340)\n\nas you know, when using remote agent, bamboo variables can be handled in script.\n\nbut, in ephemeral agent, I can handle any information about bamboo like plan trigger, commit hash or user input varibles.\n\nusually how can ephemeral agent read bamboo information?\n" }, { "author": "Shashank Kumar", "body": "Hello [???](https://community.atlassian.com/t5/user/viewprofilepage/user-id/5545873),,\n\nThere is no change in the way ephemeral agent read bamboo information, Ephemeral agent is a kind of remote agent running on a Kubernetes Pod and only difference is that it will shutdown when the Job completes based on your setting.\n\nAll your variables defined in Bamboo and any script task will work as it is, it does not depend upon which agent is executing them.\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n" } ] } ]

[ { "author": "Shashank Kumar", "body": "Hello [Mkurama](https://community.atlassian.com/t5/user/viewprofilepage/user-id/4687169),\n\nWelcome to Atlassian community.\n\nThe issue probably seems to be that the Windows remote agent is not able to establish connection with the bamboo server or it not aware of the DNS : bamboo\n\nCan you run a quick telnet command from your remote agent server to your Bamboo server and see if the connectivity is established.\n\nYou can read <https://confluence.atlassian.com/bamkb/troubleshooting-remote-agents-216957427.html> for some detailed troubleshooting steps.\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n", "comments": null } ]

[ { "author": "Jim Knepley - ReleaseTEAM", "body": "I'm curious about the --volume parameters. I would normally expect something more like\n\n```\n--volume demo_volume:/data\n```\n\n...as opposed to having the volume and mount point be the same Windows path.\n", "comments": [ { "author": "Andrzej Wisi?ski", "body": "To be honest I don't need volumes for now. But when I removed them from job setup I'm getting another error saying that my script returned -1.\n\n```\ncommand 15-Jul-2024 23:16:41 Beginning to execute external process for build 'Salesforce - Salesforce-CICD - Default Job #76 (SAL-SAL-JOB1-76)'\\n ... running command line: \\nC:\\Users\\Andrzej\\AppData\\Local\\Temp\\runInDocker7219650513349138895.sh /usr/bin/bash test.sh\\n ... in: C:\\Users\\Andrzej\\AppData\\Local\\Temp\\nsimple 15-Jul-2024 23:16:41 Failing task since return code of [C:\\Users\\Andrzej\\AppData\\Local\\Temp\\runInDocker7219650513349138895.sh /usr/bin/bash test.sh] was -1 while expected 0\n```\n\nScript is just only one echo command. Doesn't matter if its inline or file script.\n" }, { "author": "Jim Knepley - ReleaseTEAM", "body": "I interpret a -1 return code to be something dramatic, like not having enough RAM or something (not saying that's the problem, just maybe something fundamental).\n\nThe ellipsis in your output makes me think the output was truncated. Try *docker logs* for that container and hopefully it will show you the full error.\n" }, { "author": "Andrzej Wisi?ski", "body": "Maybe I'm wrong and I'll need volumes, because for some reason this runInDocker.sh script that is being copied to container tries to cd to my Windows path.\n\n# cat runInDocker984723768067173822.sh \n#!/bin/sh \ncd 'C:\\\\Users\\\\Andrzej\\\\Downloads\\\\bamboo\\\\bamboo\\\\xml-data\\\\build-dir\\\\SAL-SA-JOB1' \numask 000 \n'C:\\\\Users\\\\Andrzej\\\\Downloads\\\\bamboo\\\\bamboo\\\\temp\\\\SAL-SA-JOB1-26-ScriptBuildTask-8958078326951920057.bat' \nexit $?\n\nDo you know how I can handle this? For now I want my agent to create container, clone repository inside newly created container and run one script there.\n" } ] } ]

[ "docker" ]

[ { "author": "Shashank Kumar", "body": "Hello Rajesh,\n\nWelcome to Atlassian community.\n\nThere could be multiple reasons why Bamboo would be slow, here you have mentioned that you see this behaviour at particular timings, you can check few things.\n\n1. If you see that the behaviour is seen at particular timings, please check if there are any backup's scheduled at those timings\n\n2. Are there multiple builds which runs at those timings.\n\n3. Are there are expiry process scheduled\n\nThese are just few things which possibly can affect, the best way to check this would be to refer **\\<bamboo-home\\>logs\\>atlassian-bamboo.log** file and see what is Bamboo server during this time.\n\nYou should also monitor system resources like CPU, Heap and GC logging to check if there are any discrepancies during this time.\n\nRegards,\n\nShashank Kumar\n", "comments": null } ]

[ { "author": "Shashank Kumar", "body": "Hello [Madhankumar M](https://community.atlassian.com/t5/user/viewprofilepage/user-id/5540467),\n\nWelcome to Atlassian community\n\nI think probably the authentication is not coming correctly via Insomnia. Just to double check can you try to access this API via Postman and check if you are getting the same error?\n\nRegards,\n\nShashank Kumar\n", "comments": [ { "author": "Madhankumar M", "body": "Hi [@Shashank Kumar](/t5/user/viewprofilepage/user-id/4693340), \n\nThanks for the reply. I tried using postman too. Same response.\n" }, { "author": "Shashank Kumar", "body": "Hello Madhu,\n\nWhat errors do you see in **\\<bamboo-home\\>logs\\>atlassian-bamboo.log** file when you use the REST API from postman, does it print anything different from 401 error?\n\nRegards,\n\nShashank Kumar\n" }, { "author": "Madhankumar M", "body": "Hey, I think I got what the issue is.\n\nSometimes when I login, bamboo asks for a captcha verification. Whenever that happens, I'm getting the 401 error while using the REST API. Once I login to the UI after completing the captcha verification, the API requests are going through. \n\nIs there a way to bypass captcha while accessing the REST API?\n" } ] } ]

[ "python" ]

[ { "author": "Charlie Misonne", "body": "Hi Dilsha\n\nWhat is taking more than 5min exactly? Are you executing a REST API call to Jira that takes so long to respond?\n", "comments": null } ]

[ { "author": "Marcin Gardias", "body": "Specs for Bamboo 9.6 are compatible with 11 and 17 and use '1.8' language level by default.\n\nBamboo 10.0 is going to support JDK 17 only and you will be able to use language level 17 in specs.\n\nI hope that answers your question.\n", "comments": [ { "author": "Anders Persson", "body": "Thank you. And when will 10.0 be released?\n" }, { "author": "Marcin Gardias", "body": "Tentative date is around Aug 14, 2024\n" } ] }, { "author": "Charlie Misonne", "body": "On the [supported platforms page of Bamboo 9.6](https://confluence.atlassian.com/bamboo/supported-platforms-289276764.html) you will read that Java 17 is supported and Java 11 is being deprecated (meaning it will not be supported in future versions)\n", "comments": [ { "author": "Anders Persson", "body": "Thanks. Found that page but wasn't sure if it stated the version for the server or the Bamboo Java Spec.\n" } ] } ]

[ { "author": "Shashank Kumar", "body": "Hello Peter,\n\nWelcome to Atlassian community.\n\nI am not sure at this point what is the error, probably can you once try to resave the repository and run the plan and see if it works.\n\nYou have mentioned that there are no build logs and no errors, can you check the below files in the remote agent logs using the build key and check if you get any errors.\n\n\\<bamboo-agent-home\\>logs\\>atlassian-bamboo.log file\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n", "comments": [ { "author": "Peter Drexel", "body": "When I attempt a manual build from the Bamboo web interface for our develop branch, no commands are executed and the the status goes green within seconds. I do see these entries in the log. The referenced commit corresponds to develop.\n\n2024-07-08 09:12:56,935 INFO \\[AtlassianEvent::0-BAM::EVENTS:pool-2-thread-20\\] \\[BitbucketBuildStatusUpdater\\] Unable to sent build status update to Bitbucket: POST <https://api.bitbucket.org/2.0/repositories/delta-q/smp_auth/commit/c958454f78c2e6c89b7346586ff0f01a68a8e834/statuses/build> returned a response status of 400 Bad Request\n\n<br />\n\n2024-07-08 09:12:56,982 INFO \\[AtlassianEvent::0-BAM::EVENTS:pool-2-thread-4\\] \\[BitbucketBuildStatusUpdater\\] Unable to sent build status update to Bitbucket: POST <https://api.bitbucket.org/2.0/repositories/delta-q/smp_auth/commit/c958454f78c2e6c89b7346586ff0f01a68a8e834/statuses/build> returned a response status of 400 Bad Request\n" }, { "author": "Shashank Kumar", "body": "Hello David,\n\nThe error means Bamboo was not able to send the request back to Bitbucket after the build was triggered, but that's not the problem which you are trying to solve here.\n\nI think we'll need to see the build logs to see what the Bamboo plan is doing and also your plan structure to see what is suppose to be executed but it's not.\n\nI am not sure if you share this information publicly here, if not you can open a support request with Atlassian support.\n\nRegards,\n\nShashank Kumar\n" }, { "author": "Peter Drexel", "body": "I'm Peter BTW.\n\nIf the log you're referring to is the one accessible via the logs tab in the web interface, there is none. It's as if the build doesn't think there is anything to do.\n\nInitially, I tried to get support from Atlassian, but we no longer have a support contract.\n\nThx,\n\nPete\n" }, { "author": "Shashank Kumar", "body": "Hello Peter,\n\nApologies for calling you as David, let's do the below to investigate.\n\n1. Can you tell me at high level what are tasks which are in the particular Job.\n\n2. Is your build running on remote agent or local agent.\n\n3. You will see a build key for the plan which you are running on the Bamboo GUI, example SCRIP-TIC-56 which is {plan-key-buildnumber}\n\n4. Inside the agent which is running this build when the build starts you'll see below\n\n2024-07-08 17:06:17,703 INFO \\[2-BAM::agent1::Agent:Thread-16\\] \\[BuildAgentControllerImpl\\] SCRIP - TIC - Default Job #57 (SCRIP-TIC-JOB1-57) taken from queue.\n\n5. The below message is printed when the build completes\n\n2024-07-08 17:06:19,680 INFO \\[2-BAM::agent1::Agent:Thread-16\\] \\[RemoteResultProcessor\\] Build SCRIP - TIC - Default Job #57 (SCRIP-TIC-JOB1-57) completed on Bamboo agent. Sending results to server.\n\nCan you get all the logs in between 2 the two events for your plan and then we can check what is happening. These logs would be found on the agent which is running the build at \\<bamboo-agent-home\\>logs\\>atlassian-bamboo.log file.\n\nRegards,\n\nShashank Kumar\n" }, { "author": "Peter Drexel", "body": "1) The high level tasks are\n\na) Source Code Checkout\n\nb) Git clean\n\nc) Call batch file to set some environment variables\n\nd) Compile/link\n\ne) Call batch file to publish files\n\n2) We use remote agents\n\n3) TEST-TBP-3151\n\n4) I don't think the build ever gets to the agent (it's too quick) and if it did get to the agent, I'm not sure which agent as there is no build log\n\n5) There is no such message for this build plan\n\n![Capture.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/334100iB0F6AF97377C7395/image-size/large?v=v2&px=999 \"Capture.JPG\")\n" }, { "author": "Peter Drexel", "body": "Something I just realized is that when a new branch is created and pushed in Git, the build plan in question is not running automatically like it used to. Other expected build plans run, but not this one.\n" }, { "author": "Shashank Kumar", "body": "Hello Peter,\n\nIf the build is showing as Green, it should have been sent to an agent, we need to identify which agent. Can you check the Bamboo server application logs for the below message\n\nCan you check all the below message when the Build was trigerred and the Build completed on the Bamboo server.\n\n```\n2024-07-09 08:55:58,041 INFO [12-DelayedChangeDetectionThread:pool-13-thread-1] [ChainExecutionManagerImpl] Build SCRIP-TIC-JOB1-58 has been dispatched\n2024-07-09 08:55:58,131 INFO [ActiveMQ Session Task-5] [BuildQueueManagerImpl] Sending SCRIP-TIC-JOB1-58 to agent agent1 (id: 688129, REMOTE, online, enabled)\n2024-07-09 08:56:00,358 INFO [AtlassianEvent::1-BAM::EVENTS:pool-2-thread-12] [ChainExecutionManagerImpl] Plan SCRIP-TIC-58: SCRIP - TIC has finished executing\n```\n\nOnce you are able to identify the agent, then you can check the agent logs as mentioned in the previous steps to investigate the problem.\n\nRegards,\n\nShashank Kumar\n" }, { "author": "Peter Drexel", "body": "When I manually run the branch, here's what's added to atlassian-bamboo.log. I don't see the line you're referring to.\n\n2024-07-09 08:34:09,651 WARN \\[http-nio-8085-exec-25\\] \\[CacheAwareness$1\\] Inheriting disabledCaches:\\[com.atlassian.bamboo.CHANGE_DETECTION\\]\n\n<br />\n\n2024-07-09 08:34:10,666 INFO \\[7-DelayedChangeDetectionThread:pool-10-thread-20\\] \\[ChainExecutionManagerImpl\\] Plan TEST-TBP-3155: SSP - SSP Build has finished executing\n\n<br />\n\n2024-07-09 08:34:10,666 INFO \\[7-DelayedChangeDetectionThread:pool-10-thread-20\\] \\[PlanStatePersisterImpl\\] Updating delta states of build following TEST-TBP-3155 \n2024-07-09 08:34:10,666 INFO \\[AtlassianEvent::0-BAM::EVENTS:pool-2-thread-41\\] \\[DependencyChainListener\\] Checking children plans of \\[TEST-TBP\\] for plan TEST-TBP-3155\n\n<br />\n\n2024-07-09 08:34:10,682 INFO \\[AtlassianEvent::0-BAM::EVENTS:pool-2-thread-41\\] \\[DependencyChainListener\\] Finished checking children plans of 'SSP - SSP Build' for plan TEST-TBP-3155\n\n<br />\n\n2024-07-09 08:34:10,870 INFO \\[AtlassianEvent::0-BAM::EVENTS:pool-2-thread-29\\] \\[BitbucketBuildStatusUpdater\\] Unable to sent build status update to Bitbucket: POST <https://api.bitbucket.org/2.0/repositories/delta-q/smp_auth/commit/c958454f78c2e6c89b7346586ff0f01a68a8e834/statuses/build> returned a response status of 400 Bad Request\n\n<br />\n\n2024-07-09 08:34:10,916 INFO \\[AtlassianEvent::0-BAM::EVENTS:pool-2-thread-40\\] \\[BitbucketBuildStatusUpdater\\] Unable to sent build status update to Bitbucket: POST <https://api.bitbucket.org/2.0/repositories/delta-q/smp_auth/commit/c958454f78c2e6c89b7346586ff0f01a68a8e834/statuses/build> returned a response status of 400 Bad Request\n" }, { "author": "Shashank Kumar", "body": "Hello Peter,\n\nIt's really strange to not have the Job startup logs and difficult to tell what's happening without the support zip.\n\nLet's do couple of quick things.\n\n1. Shutdown Bamboo and Restart it, this will recreate the plan cache and let's see if you get the same issue.\n\n2. Clone the plan and disable the original plan and run the clone plan and see if you see the same behaviour.\n\n3. You can also try to change the linked repository for the plan and see if you see the same issue.\n" }, { "author": "Peter Drexel", "body": "1) I have tried this several times already with no effect\n\n2) I just did this and the new plan behaves the same way\n\n3) I'm not exactly sure what to do here. Do you want me to delete the plan's repository and then re-add it? Or, do you want me to create a new linked repository and then replace the plan's repository with the newly linked one?\n" }, { "author": "Peter Drexel", "body": "Should I ask our admin to create a support zip? Is there a link on how to do that?\n" }, { "author": "Shashank Kumar", "body": "Hello Peter,\n\nYou can create a new linked repository and then replace the plan's repository with the newly linked one and then run and see what happens.\n" }, { "author": "Shashank Kumar", "body": "This is a public forum and we should not upload any support zip for your own safety.\n" }, { "author": "Peter Drexel", "body": "OK, I figured it out. Apologies to all for not realizing it sooner. It turns out the job within the plan was disabled. I only discovered this because I went to recreate the plan instead of cloning it and I noticed under the Job Details tab that it had been disabled. I'm not sure when/how/who disabled it, but once it was re-enabled, the plan executed as expected. Thanks for all the help.\n" }, { "author": "Shashank Kumar", "body": "Thanks Peter for letting us know the real issue.\n\nYou can check the Audit logs for the plan to check when was the Job disabled and by whom.\n\nRegards,\n\nShashank kumar\n" } ] } ]

[ { "author": "Shashank Kumar", "body": "Hello garrellj,\n\nWelcome to Atlassian community.\n\nThis is expected because this build will return the name for only Plan branches and not the default branch ( main branch ).\n\nAs per the description at [Bamboo Variables](https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html)\n\n|----------------------------|----------------------------------------------------------------|\n| bamboo.shortPlanBranchName | The name of the current plan branch where the job is being run |\n\nFor the default branch if you need the same you can use\n\n|-----------------------------------------|-----------------------------------------------------------------|\n| bamboo.planRepository.branchDisplayName | The name of the branch displayed in the branch details section. |\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n", "comments": null } ]

[ { "author": "Charlie Misonne", "body": "Hi [@Oleksii Kotukhov](/t5/user/viewprofilepage/user-id/5533174) and welcome to the Atlassian Community!\n\nI'm not aware of such a setting. Canceling a build each time a new one starts does not sound ideal. What if your build is quite long and every time it almost completes there is a new push. Theoretically you could end up with commits all day long without a single completed build.\n\nInstead you could use the **quiet period** setting: [Globally enabling the repository quiet period \\| Bamboo Data Center 9.6 \\| Atlassian Documentation](https://confluence.atlassian.com/bamboo/globally-enabling-the-repository-quiet-period-1236444136.html)\n\nWith this setting Bamboo will not execute a build immediately but it will wait for some time to allow consecutive pushes to be built in a single run.\n", "comments": [ { "author": "Oleksii Kotukhov", "body": "Hello [@Charlie Misonne](/t5/user/viewprofilepage/user-id/502263) we have cases when the build can take a long time to be executed. This can lead to a long queue with scheduled builds for the same branch. So I'm looking for some feature to allow canceling such \"duplicates\" automatically.\n" }, { "author": "Charlie Misonne", "body": "Hi Oleski,\n\nWell nothing like that exists so you'd have to create your own plugin.\n\nOr creating external script listening checking the queue with this API endpoint: [Get api latest queue](https://developer.atlassian.com/server/bamboo/rest/api-group-api/#api-api-latest-queue-get)and [this one](https://developer.atlassian.com/server/bamboo/rest/api-group-api/#api-api-latest-queue-projectkey-buildkey-buildnumber-delete) to stop a build if another one has been queued.\n\nYou can also rethink your build process: do you really need to build on every commit? Why not just every hour, or every 2 hours, or... \nOr you could only build when a pull request is created. \nJust some ideas :-)\n" } ] }, { "author": "Marcin Gardias", "body": "The feature is coming in Bamboo 10.\n", "comments": [ { "author": "Oleksii Kotukhov", "body": "Is there any official reference I can use? \nThank you in advance\n" }, { "author": "Marcin Gardias", "body": "The official release is still few weeks away, but we've just published a release candidate: <https://community.developer.atlassian.com/t/bamboo-data-center-10-0-early-access-program-release/81426>\n" } ] } ]

[ { "author": "Shashank Kumar", "body": "Hello Gouri,\n\nWelcome to Atlassian community.\n\nStarting from Bamboo 9.5, the option to install new apps using the Upload app button on the Manage apps page or with the REST API is disabled by default. This change was made to prevent the inadvertent upload of potentially harmful files to your Bamboo instance.\n\nTo enable app installation with the Upload app button, you will have to set a specific system property as detailed in the release page in [Bamboo 9.5 release notes - Installing apps with the Universal Plugin Manager](https://confluence.atlassian.com/bambooreleases/bamboo-9-5-release-notes-1333337319.html#Bamboo9.5releasenotes-InstallingappswiththeUniversalPluginManager), i.e, add the property to JVM_SUPPORT_RECOMMENDED_ARGS; \n\n```\n-Dupm.plugin.upload.enabled=true \n```\n\nThe file to add the property is located in \"***\\<Bamboo-install\\>/bin/setenv.sh*** \". You can find more information on configuring system properties in this [link](https://confluence.atlassian.com/bamboo0905/configuring-your-system-properties-1345818971.html), you can refer the attached link to get details if you are using Windows environment.\n\nRegards,\n\nShashank kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n", "comments": null }, { "author": "Matt Simmons", "body": "For the record, this is a totally ridiculous solution. If there's a security problem in the feature that people use, the answer should not be to disable the otherwise necessary feature until someone needs it, then require them to re-enable the still-broken feature. \n\nFix the problem instead. Is there a ticket tracking the remediation of the underlying security problem in the upload tool?\n", "comments": [ { "author": "Shashank Kumar", "body": "Hello Matt,\n\nThe idea was to prevent unwanted uploads of potentially malicious files to your Bamboo instance, with the Upload apps option anyone can upload any files on your Bamboo Instance.\n\nCurrently there is no ticket raised for any further work on this, customers are requested to follow the workaround.\n\nRegards,\n\nShashank Kumar\n" }, { "author": "Matt Simmons", "body": "So with the Upload Apps option enabled, any user, admin or otherwise, can upload malicious files to the instance?\n" }, { "author": "Shashank Kumar", "body": "Hello Matt,\n\nThe Upload Apps option is visible only for Bamboo Admins and not for others this reduces the risks for anyone accessing this functionality.\n\nThis Functionality allows you to upload files of type .jar or .obr, while uploading Bamboo does not check what is inside the jar as it is custom applications developed outside of Bamboo.\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/339683iEB4F784D53F8654A/image-size/large?v=v2&px=999 \"image.png\") \n\nRegards,\n\nShashank Kumar\n" } ] } ]

[ { "author": "Shashank Kumar", "body": "Hello [Shreyank](https://community.atlassian.com/t5/user/viewprofilepage/user-id/5528820),\n\nWelcome to Atlassian community.\n\nFor details about Skipped test currently there is a feature request raised, please see [BAM-20948 Build result summary should show details about skipped/Quarantined tests](https://jira.atlassian.com/browse/BAM-20948) unfortunately this has not gathered much attention.\n\nFor the difference in count there are few knows issues with the way Bamboo displays the number of tests, I am not sure if your issue is related to one of those, probably it will need some investigation with the build results, logs and the test xml to see the issue, I would suggest to raise a ticket with Atlassian support to check this.\n\nOne of the known issues : <https://jira.atlassian.com/browse/BAM-11366>\n\nRegards,\n\nShashank kumar\n\n**\\*please don't forget to Accept the answer if your query was answered\\*\\***\n", "comments": null } ]

[ { "author": "Shashank Kumar", "body": "Hello Okuhle,\n\nWelcome to Atlassian Community.\n\nI am not sure on your setup, but probably you might have enabled \"Clean working directory after each build\" on the Job where the File is generated, can you uncheck this option by going to the Job configuration and see if the file is left after the build completes.\n\nRegards,\n\nShashank Kumar\n", "comments": null } ]

[ "java", "selenium" ]