question
dict | answers
listlengths 1
27
| url
stringlengths 66
601
| tags
listlengths 1
15
⌀ |
|---|---|---|---|
{
"author": "Rosa M Fossi",
"title": "Atlas auto-created a Team?",
"body": "Hello Everyone! I'm not certain how these \"teams\" (the team name is just list of users in the team) appeared in my Atlas. \nIs this something that someone created manually or were they auto-added by Atlas?\n\n![atlas-teams-001.png](/t5/image/serverpage/image-id/306712i5704C1156FBC17E3/image-size/large?v=v2&px=999 \"atlas-teams-001.png\")\n"
} | [
{
"author": "Nicola Sun",
"body": "Hi Rosa,\n\nThese teams would've been created by someone in your organisation. When a team is created, it can be used across all your products and will be visible to your entire organisation.\n\nTeams can be created via the \"Teams\" menu item in the top navigation (Teams \\> Create a team).\n\nLet me know if you have any further questions.\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Atlas-questions/Atlas-auto-created-a-Team/qaq-p/2611000 | [
"team"
]
|
{
"author": "Carlos Garcia Navarro",
"title": "Start and target dates are not synchronizing correctly between JPD and Atlas",
"body": "Hi there!\n\nI'm having an issue where the dates in Jira Product Discovery don't synchronize correctly with the ones in Atlas, even though the two products are synchronized. I can see the Atlas logo in JPD date fields, and a message that says that the dates are being overridden by Atlas, but in reality the dates are not matching Atlas start and target dates. Is anyone else experiencing this? Any idea on how to troubleshoot? Thanks!\n\nJPD:\n\n![Screenshot 2024-02-15 at 9.11.59?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/306674i9641B9038F91EF4E/image-dimensions/440x117?v=v2 \"Screenshot 2024-02-15 at 9.11.59?AM.png\")\n\nCorresponding project in Atlas:\n\n![Screenshot 2024-02-15 at 9.13.15?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/306676iCD02663C8AA3FCDC/image-dimensions/282x67?v=v2 \"Screenshot 2024-02-15 at 9.13.15?AM.png\")![Screenshot 2024-02-15 at 9.13.33?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/306677i16CD2152AD36A9F5/image-dimensions/220x95?v=v2 \"Screenshot 2024-02-15 at 9.13.33?AM.png\")\n"
} | [
{
"author": "Nicola Sun",
"body": "Hi Carlos,\n\nSorry to hear you are experiencing this, our team is looking into the issue now. Can I confirm that you are linking the same Atlas ticket?\n",
"comments": [
{
"author": "Carlos Garcia Navarro",
"body": "Thanks, [@Nicola Sun](/t5/user/viewprofilepage/user-id/5429203) ! Yes. Let me know if I can provide more information.\n"
},
{
"author": "Nicola Sun",
"body": "Hi Carlos, I've checked with my team and it seems like we do not support date syncing between Jira Product Discovery and Atlas today.\n\nI've added this feedback to our backlog and will help prioritise with the team.\n\nThanks,\n\nNicola\n"
},
{
"author": "Carlos Garcia Navarro",
"body": "Thanks, [@Nicola Sun](/t5/user/viewprofilepage/user-id/5429203) . Is this a bug, or a feature that hasn't been implemented at all?\n"
}
]
}
]
| https://community.atlassian.com/t5/Atlas-questions/Start-and-target-dates-are-not-synchronizing-correctly-between/qaq-p/2610802 | null |
{
"author": "Mona Slaunwhite",
"title": "is there a way to configure Atlas email updates ?",
"body": "Hello,\n\nSeveral followers on our Atlas project are receiving emails every time someone adds an update, a new decision, a new risk etc.. and this is in addition to the weekly digest.\n\nMost users only want to receive the weekly digest and not receive an email every time someone adds an update. Can this be configured somehow ?\n\nWe are trying to get our teams to adopt the use of Atlas, but the frequent emails are annoying several team members.\n\nAppreciate any advice.\n\nThank you !\n"
} | [
{
"author": "Nicola Sun",
"body": "Hi Mona, email configurations are only available for digests and reminders today.\n\nI have added your feedback to our backlog and will work with the team to prioritise.\n",
"comments": [
{
"author": "Jesper",
"body": "Just want to add... Been using it for a couple of weeks now, and already starting to add filters in my inbox to achieve all the emails coming from Atlas. \nEvery single comment is a new mail, other team members are talking about unfollowing the projects altogether.\n\nIt's so much noise, to an already noisy day. \n\nSo I really hope this is sorted out soon.\n"
},
{
"author": "Taronish Pithawala",
"body": "We too have had executives who *want* to receive the weekly digest unfollow projects because they receive too many emails about new learnings, etc. \n\nThis is becoming a huge blocker to adoption for us. The tools are great - the \"follower\" experience is awful! \n\n<br />\n"
},
{
"author": "Paavo P_",
"body": "Yep, it seems that these emails are also mixing the information, e.g. in this example the user created a risk, but the notification is talking about new learning?\n\nIt's a bit hard to troubleshoot, since there is no way how to re-configure these email templates? ?\n\n![example-how-Atlas-is-mixing-up-notifications-between-risks-and-learnings-for-example.png](https://community.atlassian.com/t5/image/serverpage/image-id/314828iD5F4719C69325DEE/image-size/large?v=v2&px=999 \"example-how-Atlas-is-mixing-up-notifications-between-risks-and-learnings-for-example.png\")\n"
},
{
"author": "Mona Slaunwhite",
"body": "just checking in to see if there has been any progress on this; most of our team has now abandoned the use of Atlas due to this issue\n"
}
]
}
]
| https://community.atlassian.com/t5/Atlas-questions/is-there-a-way-to-configure-Atlas-email-updates/qaq-p/2606408 | null |
{
"author": "DamCoder",
"title": "Has anyone created a pilot program to onboard Atlas?",
"body": "We prefer to try out products before rolling them out to the entire workforce.\n\nHas anyone turned on Atlas and been able to restrict access to it to a group in Jira?\n"
} | [
{
"author": "Carlos Garcia Navarro",
"body": "Hi [@DamCoder](/t5/user/viewprofilepage/user-id/735031) ,\n\nYou could just assign the Atlas licenses only to the people running the pilot.\n",
"comments": null
},
{
"author": "Brant Schroeder",
"body": "[@DamCoder](/t5/user/viewprofilepage/user-id/735031)\n\nCurrently there is not a way to restrict access to the product other than projects (<https://intercom.help/atlas-by-atlassian/en/articles/6403749-restrict-the-viewing-and-editing-of-projects> ). Everything else, like goals is public.\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Atlas-questions/Has-anyone-created-a-pilot-program-to-onboard-Atlas/qaq-p/2605273 | null |
{
"author": "System Admin",
"title": "When using Jira integration do you loose Answers functionality?",
"body": "When setting up the integration I no longer see the Answers button in slack on tickets created that are sent to Jira.\n\nI do not see it mentioned in the documentation\n\n<https://plz.halp.com/article/2f4ix4h0qp-connect-to-multiple-jira-projects>\n\nIt just says:\n\n\"Once you connect a Queue to to a Jira Project, you will no longer be able to edit Halp Fields, Forms, or Statues on that Queue. This is all managed in your Jira Project's settings and synced back to Halp.\"\n"
} | [
{
"author": "Jensen Fleming",
"body": "Hey [@System Admin](/t5/user/viewprofilepage/user-id/4933773) -- We don't show that button until you have an answer added. Once you create an answer in that queue, the Choose Answer button will appear :)\n",
"comments": [
{
"author": "System Admin",
"body": "Ah excellent. It was confusing because with the normal Halp triage the answer button shows even without answers set.\n\nI added an answer and sure enough it shows now :) Thanks!\n"
}
]
}
]
| https://community.atlassian.com/t5/Assist-questions/When-using-Jira-integration-do-you-loose-Answers-functionality/qaq-p/2038875 | null |
{
"author": "karthikeyan",
"title": "couldn't able to add queue in halp for teams",
"body": "while i am trying to configure the TEAMS app by adding queue in HALP it is not allowing me to do so... \nbelow is the error am getting while configuring it. \nNOTE- already i configured a channel from slack in halp \n\n**ERROR-\n\"We could not authenticate this integration for the site you selected.** \n**That site is already connected to another Halp instance. You'll need to disconnect from that instance before you authenticate here\".**\n"
} | [
{
"author": "Andrew Homeyer",
"body": "Unfortunately only Slack *or* Teams can be connected to a JSM site, not both.\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Assist-questions/couldn-t-able-to-add-queue-in-halp-for-teams/qaq-p/2033960 | null |
{
"author": "Sub",
"title": "How to get the ticket list assigned to oneself",
"body": "We have been starting to run Halp our organization recently. \nOur Agents want to check the tickets assigned themselves because a lot of tickets are created for one day.\n\nCan we make the list assigned to ourselves? In that case, can we do it on Slack?\n"
} | [
{
"author": "Tori Stitt",
"body": "Hey [@Sub](/t5/user/viewprofilepage/user-id/4688724) that's a great question, you can view them in Slack through Assist's App home. \n\nIn Slack, go to your Apps section in Slack\\>search or select Assist. This will take you to the App home section of Assist.\n\nOnce in Assist's App home, you'll default to a list view of all your active tickets. In the second section from the top, under \"Raise a Request\". There is a section called \"Filter\" and to the right, there is a button that says \"Filter Tickets\".\n\n![Screen Shot 2022-05-02 at 10.35.36 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/195517iA25217CC52160724/image-size/large?v=v2&px=999 \"Screen Shot 2022-05-02 at 10.35.36 AM.png\")\n\nClick on the \"Filter Tickets\" button and you will get a dropdown option to select which ticket view type you'd like to filter to see. Scroll down to \"Assignment\" and select \"Assigned to me\".\n\n![Screen Shot 2022-05-02 at 10.21.49 AM (1).png](https://community.atlassian.com/t5/image/serverpage/image-id/195518iF7FE9D85E30252B1/image-size/large?v=v2&px=999 \"Screen Shot 2022-05-02 at 10.21.49 AM (1).png\")\n\nFrom there, click confirm and the selected tickets will populate in their Assist App home in Slack.\n\nHope this helps!\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Assist-questions/How-to-get-the-ticket-list-assigned-to-oneself/qaq-p/2016778 | [
"assist",
"issue",
"slack"
]
|
{
"author": "Dan Rico",
"title": "Prevent Disclaimer from being appended to Halp Auto-Replies",
"body": "We recently started testing a appended disclaimer for all inbound emails from external addresses.\n\nThere is an email alias that is used for creating tickets and a forwarding rule exists to forward the emails to the inbound Halp email address.\n\nWhen Halp auto-replies to the user from that internal address, the disclaimer is appended because Halp's SendGrid email is responding on behalf of the internal address (and is authorized to do so).\n\nWhat is the correct method for excluding this sender from getting the disclaimer appended to the emails without increasing up the risk for possible spoofing? Are there any identifying values in the Halp email headers that can be used to do this?\n\nThe current flow is:\n\n1. User emails \"[email protected]\"\n2. Halp auto-replies from \"[email protected]\"\n3. Email gets disclaimer appended because \"[email protected]\" is the alias that Halp's SendGrid is using.\n\nSide note: DKIM and DMARC are being utilized as well to ensure that Halp is authorized to send on behalf of the \"[email protected]\" account - if that helps give any more defining characteristics.\n"
} | [
{
"author": "Fletcher Richman",
"body": "Hi Dan!\n\nHalp does not have custom email headers, but you should be able to look at the DKIM Signature Headers and filter based on this value:\n\n```\ninbound.halp-mail.com\n```\n\nLet us know if that doesn't work!\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Assist-questions/Prevent-Disclaimer-from-being-appended-to-Halp-Auto-Replies/qaq-p/2009288 | [
"auto-reply",
"email"
]
|
{
"author": "Steven Gibone",
"title": "Separate ticket name from first message",
"body": "Hi,\n\nI didn't know how to formulate my question better but here's what I mean:\n\nTickets have name which is the message a user send in Slack but this is not great since they can be quite long and usually starts with \"Hello, I have this issue when ...\" and then it becomes difficult to look for a ticket in particular. For this reason we are forcing the use of forms with a description field but this time the issue is that users don't see the description field. They only see the title field, which is also the first message of the conversation.\n\nWhat would be nice is to have a way to set the name of the ticket whatever field I want and the first message of the conversation something else. Or simply to allow users to see another field\n\nWill such thing be possible or even better is there something I'm missing that would solve my problem ?\n\nThank you :)\n"
} | [
{
"author": "Eric Murn",
"body": "Check out the Jira automation rule described [here](https://plz.halp.com/article/bijuiy01g7-jira-automations-halp#flip_the_summary_and_description). That sets the issue summary to whatever you'd like, i.e. *Halp Request from {{reporter.displayName}}*, and puts the user's Slack message in the issue description.\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Assist-questions/Separate-ticket-name-from-first-message/qaq-p/2001431 | null |
{
"author": "nberanger-tgam",
"title": "Is there any way to strip code from an email before it posts to Slack?",
"body": "Right now when a ticket is created via email, it seems to include a bunch code before the message. Here is an example:\n\n```\n<!--\n/* Font Definitions */\n@font-face\n {font-family:\"Cambria Math\";\n panose-1:2 4 5 3 5 4 6 3 2 4;}\n@font-face\n {font-family:Calibri;\n panose-1:2 15 5 2 2 2 4 3 2 4;}\n/* Style Definitions */\np.MsoNormal, li.MsoNormal, div.MsoNormal\n {margin:0in;\n margin-bottom:.0001pt;\n font-size:11.0pt;\n font-family:\"Calibri\",sans-serif;}\na:link, span.MsoHyperlink\n {mso-style-priority:99;\n color:#0563C1;\n text-decoration:underline;}\na:visited, span.MsoHyperlinkFollowed\n {mso-style-priority:99;\n color:#954F72;\n text-decoration:underline;}\np.msonormal0, li.msonormal0, div.msonormal0\n {mso-style-name:msonormal;\n mso-margin-top-alt:auto;\n margin-right:0in;\n mso-margin-bottom-alt:auto;\n margin-left:0in;\n font-size:12.0pt;\n font-family:\"Times New Roman\",serif;}\nspan.EmailStyle18\n {mso-style-type:personal;\n font-family:\"Calibri\",sans-serif;\n color:windowtext;}\nspan.EmailStyle19\n {mso-style-type:personal-reply;\n font-family:\"Calibri\",sans-serif;\n color:#1F497D;}\n.MsoChpDefault\n {mso-style-type:export-only;\n font-size:10.0pt;}\n@page WordSection1\n {size:8.5in 11.0in;\n margin:1.0in 1.0in 1.0in 1.0in;}\ndiv.WordSection1\n {page:WordSection1;}\n-->\n```\n\nIs there any way to avoid this? It can make the tickets very cluttered and hard to read.\n"
} | [
{
"author": "Fletcher Richman",
"body": "Looks like our email parser is not handling the HTML of an email very well. We do have a known issue right now for O365 users due to the way those emails are formatted. Are you using O365?\n\nIs this happening on every ticket or just some? Please open a [support request](https://www.atlassian.com/software/halp/contact) and we will look into it, may be a bug.\n",
"comments": [
{
"author": "nberanger-tgam",
"body": "Yep, we are indeed on O365. We are just running a pilot of Halp right now, so no access to support yet. Good to know that this shouldn't be included though. Once we sign our contract, I'll reach out to support if this is still happening.\n\nThanks!\n"
},
{
"author": "nberanger-tgam",
"body": "Just found out that even though we are on a trial, we still have access to Halp support :-)\n"
}
]
}
]
| https://community.atlassian.com/t5/Assist-questions/Is-there-any-way-to-strip-code-from-an-email-before-it-posts-to/qaq-p/1989220 | [
"code",
"email",
"font",
"format",
"mail",
"remove"
]
|
{
"author": "nberanger-tgam",
"title": "Can I use text formatting with Halp responses in Slack?",
"body": "I am working on getting some recipes and auto-replies set up, and would like to use some text formatting to make things look better. Is that an option? I can't seem to find any info on this.\n\nIn particular, I really want to be able to use hyperlinks to point to some of our internal docs on our SharePoint. The links are rather long and ugly, so hyperlinks would really help.\n"
} | [
{
"author": "Mikael Sandberg",
"body": "Hi [@nberanger-tgam](/t5/user/viewprofilepage/user-id/4846264),\n\nWelcome to Atlassian Community!\n\nYes, you can use text formatting in your auto-answers. Halp is using the [Slack mrkdwn](https://api.slack.com/reference/surfaces/formatting) formatting, so for example to add a link just use\n\n\\<[http://www.example.com\\|](http://www.example.com|)This message \\*is\\* a link\\>\n",
"comments": [
{
"author": "nberanger-tgam",
"body": "Thank you very much sir.\n"
}
]
},
{
"author": "nberanger-tgam",
"body": "Just heard back from my contact at Halp, and apparently you can use the Slack formatting:\n\n<https://api.slack.com/reference/surfaces/formatting#linking-urls>\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Assist-questions/Can-I-use-text-formatting-with-Halp-responses-in-Slack/qaq-p/1986572 | [
"format",
"link",
"slack",
"text"
]
|
{
"author": "Carlos Garcia Navarro",
"title": "I can't delete a Halp SLA",
"body": "Hello,\n\nWhen I try to disable or to delete the Halp SLA, there is an error message, but I don't see more details. Where can I find more details about the error, and why wouldn't be possible to disable/delete it?\n\n![Screen Shot 2022-03-06 at 7.26.05 PM (2).png](https://community.atlassian.com/t5/image/serverpage/image-id/186626i48FB37640EC17A7A/image-dimensions/559x315?v=v2 \"Screen Shot 2022-03-06 at 7.26.05 PM (2).png\")![Screen Shot 2022-03-06 at 7.26.18 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/186625i6990ADE4FD10A1B3/image-size/large?v=v2&px=999 \"Screen Shot 2022-03-06 at 7.26.18 PM.png\")\n"
} | [
{
"author": "Nicole Pitaro",
"body": "Hey [@Carlos Garcia Navarro](/t5/user/viewprofilepage/user-id/1031232) -- Hmm that's strange. Someone on our team is investigating this and we'll be in touch!\n",
"comments": [
{
"author": "Nicole Pitaro",
"body": "Hey [@Carlos Garcia Navarro](/t5/user/viewprofilepage/user-id/1031232) -- Our team hasn't yet located any issue that would be causing this. Would you mind submitting your info here so they can get some more details and investigate further? <https://www.atlassian.com/software/halp/contact#/>\n"
},
{
"author": "Carlos Garcia Navarro",
"body": "Thanks, Nicole. Done!\n\nAs an update, it's working now, but I submitted the details in the ticket so your team can take a look. Thanks!\n"
}
]
}
]
| https://community.atlassian.com/t5/Assist-questions/I-can-t-delete-a-Halp-SLA/qaq-p/1963768 | null |
{
"author": "Carlos Garcia Navarro",
"title": "Is it possible to edit Halp SLAs?",
"body": "Hi there-\n\nSorry if this has been asked before, but I couldn't find an answer. Is it possible to edit an SLA in Halp/Assist?\n\nI can see only an option to delete existing ones:\n\n![Screen Shot 2022-03-06 at 7.22.14 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/186623iAFAF5F794ACD4A33/image-size/large?v=v2&px=999 \"Screen Shot 2022-03-06 at 7.22.14 PM.png\")\n\nThanks,\n"
} | [
{
"author": "Nicole Pitaro",
"body": "Hey [@Carlos Garcia Navarro](/t5/user/viewprofilepage/user-id/1031232) -- It is not possible to edit an existing SLA.\n",
"comments": [
{
"author": "Carlos Garcia Navarro",
"body": "Ok, thanks, Nicole. Is there any plan to make SLAs editable?\n"
},
{
"author": "Fletcher Richman",
"body": "It's a feature request we are tracking. To give you some insight on why we don't already support it - editing SLAs has a surprising level of complexity. To give you a sense of why, consider the following example: \n\nLets say you create an SLA with a 24 hour \"timer\". So 24 hours from now, it should notify Slack/Teams that there has been a breach.\n\nA ticket is created, and the 24 hour timer starts.\n\n15 hours later, let's say you edit the SLA and change that timer to be 12 hours instead of 24 hours.\n\nWhat should happen to the notifications that were going to send for that ticket that was created? It's technically already been 15 hours, so has it breached the 12 hour limit that you just edited? Should a notification get sent?\n\nThat's just one example of the complexity that gets created, and so we decided to get the feature out the door faster we'd just allow for creation and deletion of SLAs, figuring that users could always just delete and SLA and make a new one, and then it would be clear what would happen.\n"
}
]
}
]
| https://community.atlassian.com/t5/Assist-questions/Is-it-possible-to-edit-Halp-SLAs/qaq-p/1963758 | null |
{
"author": "Carlos Garcia Navarro",
"title": "Does Halp support multilogic when defining ticket recipes?",
"body": "Hello,\n\nIs it possible to create a ticket recipe with a trigger with two conditions, e.g. where 'field A' = X and 'field B' = Y ? Thanks\n"
} | [
{
"author": "Nicole Pitaro",
"body": "Hi [@Carlos Garcia Navarro](/t5/user/viewprofilepage/user-id/1031232) -- No, Halp does not support that at this time.\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Assist-questions/Does-Halp-support-multilogic-when-defining-ticket-recipes/qaq-p/1963500 | null |
{
"author": "Carlos Garcia Navarro",
"title": "Is it possible to group ticket recipes in the Halp recipe builder?",
"body": "Hi there-\n\nThe problem is that there are many ticket recipes in the recipe builder. If I could group them, it would make it easier to work with them (e.g. to find them to troubleshoot). Is it possible? Thanks!\n"
} | [
{
"author": "Nicole Pitaro",
"body": "Hi [@Carlos Garcia Navarro](/t5/user/viewprofilepage/user-id/1031232) -- No, we don' t offer the option to group them at this time, but you can sort recipes by trigger or action.\n",
"comments": [
{
"author": "Carlos Garcia Navarro",
"body": "Ok, thanks Nicole!\n"
}
]
},
{
"author": "Sarang Ardhapurkar",
"body": "Hi, \n\nI would also be really interested in this feature. We have over 30 recipes and are looking to add several more. It would be really nice if we could group them by Queue or Project. \n\nIdeally, it would be nice if we could add a tag to each recipe and then group them using the tags.\n\nIs there a way we can put in a Feature Request for HALP?\n\nThanks\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Assist-questions/Is-it-possible-to-group-ticket-recipes-in-the-Halp-recipe/qaq-p/1963485 | null |
{
"author": "lisosimar",
"title": "Lantronix EDS16PR (EDS16PR) open serial port",
"body": "How do I know which tcp port maps to a serial port in the device?\n\nAssuming then I can do something like:\n\ntelnet 192.168.1.10 10001\n\nview serial output....\n\nThe config looks like\n\nshow lines \nCELLDYN RUBY (Line 1): \nRS232, 9600, None, 8, 1, None \nTunnel Connect Mode: Disabled, Accept Mode: Active \nBeckman DxC 700 AU (Line 2): \nRS232, 9600, None, 8, 1, None \nTunnel Connect Mode: Disabled, Accept Mode: Active \nBeckman DxI 600 (Line 3): \nRS232, 9600, None, 8, 1, None \nTunnel Connect Mode: Disabled, Accept Mode: Active\n"
} | [
{
"author": "Nic Brough -Adaptavist-",
"body": "Welcome to the Atlassian Community!\n\nI think you are in the wrong place. This Community is here to talk about Atlassian, not that hardware you have mentioned. I suspect you've been looking at a site, probably built on Atlassian services, about the hardware, and you've clicked on \"help with Atlassian stuff\" instead of \"help with hardware\".\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Assist-questions/Lantronix-EDS16PR-EDS16PR-open-serial-port/qaq-p/1961478 | null |
{
"author": "Carlos Garcia Navarro",
"title": "Can I manually connect a Jira ticket to a Halp ticket?",
"body": "Hi there-\n\nI've done a number of configurations with Halp/Assist, but I don't know if it's possible to manually connect a Halp ticket with an existing Jira ticket.\n\nFor more details, when users post a question for the first time, I've configured an integration that creates a Jira ticket that is then linked to the Halp one. In some cases, though, a Jira does exist and I'd like to connect them manually so they stay in sync as well. Thanks\n"
} | [
{
"author": "Jensen Fleming",
"body": "Hey [@Carlos Garcia Navarro](/t5/user/viewprofilepage/user-id/1031232) -- that isn't possible. Assist can only create new Jira tickets, not link to existing ones. You can, however, send tickets created from Jira into Slack via Halp/Assist. That way the ticket will be in the triage channel and in a DM from the requester for follow ups.\n",
"comments": [
{
"author": "Carlos Garcia Navarro",
"body": "Interesting, thanks Jensen. How do you do that?\n"
},
{
"author": "Carlos Garcia Navarro",
"body": "I'd be okay if there is no Halp ticket in Halp/Assist, but I can update the Jira ticket from Slack (where the conversation with the requester and others would happen).\n"
},
{
"author": "Jensen Fleming",
"body": "The best way is to opt into our [new integration experience](https://community.atlassian.com/t5/Halp-articles/Introducing-a-new-amp-improved-Jira-integration-experience/ba-p/1947829), and its just a little toggle per request type.\n\nOtherwise you need to make 2 recipes per request type.\n\n- When a ticket is created from an integration, RT, create a ticket in halp\n\n- When a ticket is created from an integration, RT, send the ticket to a queue.\n\nI'd recommend opting into the new experience :)\n"
},
{
"author": "Paul Romero",
"body": "[@Jensen Fleming](/t5/user/viewprofilepage/user-id/4058269) do you have details on the 'toggle'. I'd like any ticket created in JSM to open a Halp Ticket and notify the Slack Triage channel. Right now I have this working for items coming in from Slack and Intercom, but items coming from email are creating a Slack ticket but not a Halp one.\n"
},
{
"author": "Jensen Fleming",
"body": "[@Paul Romero](/t5/user/viewprofilepage/user-id/4794796) -- I'd recommend signing up for the [JSM Chat beta](https://community.atlassian.com/t5/Jira-Service-Management-articles/EARLY-ACCESS-PROGRAM-Conversational-ticketing-in-Jira-Service/ba-p/1941267) (coming out of beta soon).\n"
}
]
}
]
| https://community.atlassian.com/t5/Assist-questions/Can-I-manually-connect-a-Jira-ticket-to-a-Halp-ticket/qaq-p/1963484 | null |
{
"author": "Esteban Halabi",
"title": "Trouble installing halp",
"body": "Hey everyone, a Client is requesting to integrate halp with their slack. I've sent the step by step guide to their IT support team since they are the admins to their slack.\n\nHowever, we've hit a roadblock.\n\nThey sent me a screenshot that and they are unsure how to proceed. Unfortunately the only person in my team that has used halp before is unreachable atm.\n\nthe screenshot reads:\n\n\"you've tried to create a ticket but your team does not have a triage channel set. You do not have an admin set on your team. please contact [email protected] to resolve this issue\"\n\nFirst part is pretty straight forwards they have yet to create the triage channel. however\n\nhow do we set an admin? is the only solution to go through halp support?\n\nthank you\n"
} | [
{
"author": "Nicole Pitaro",
"body": "Hi [@Esteban Halabi](/t5/user/viewprofilepage/user-id/4718090) -- yes, since agents don't have permissions to promote other agents to admin, they will need need to reach out to our support team. Once our support team has the account name and the name of the user they can give admin access!\n",
"comments": [
{
"author": "Esteban Halabi",
"body": "Thank you!\n"
}
]
},
{
"author": "Emel Do?rus?z",
"body": "Hello Esteban,\n\nSince Halp is not available anymore, you may want to use Actioner's ticketing solution instead. It lets you run all your operations from within Slack.\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
}
]
| https://community.atlassian.com/t5/Assist-questions/Trouble-installing-halp/qaq-p/1961431 | [
"integration",
"slack"
]
|
{
"author": "Bruce Anderson [Administrator]",
"title": "How to change the Triage Channel",
"body": "We are new to Halp, and loving it so far. One issue we have though, is when we set it up we selected a channel for the triage channel that is used for other things. We wish to change the triage channel now, but can't see a way to do that. Can anyone confirm how that is possible? I didn't want to uninstall and reinstall.\n"
} | [
{
"author": "Tomislav Tobijas",
"body": "Hi Bruce,\n\nTo use a different Slack channel as a triage channel, simply invite the Assist app to the channel you wish to set as a new triage channel. For that, you can use **/invite @Assist** command in that Slack channel.\n\nNow you'll have two triage channels - the new one where you've just added the Assist app, and the 'old' one that you don't want to use as a triage channel.\n\nThe last step would be to remove the Assist app from the channel you don't wish to use as a triage channel anymore. To do that, simply use **/remove @Assist** command in channel chat.\n\nHope this helps!\n",
"comments": [
{
"author": "Leigh Wolf",
"body": "And how would you do this for teams?\n"
},
{
"author": "Tomislav Tobijas",
"body": "Hi [@Leigh Wolf](/t5/user/viewprofilepage/user-id/4004992)\n\nWe're mainly Slack users and I don't have app permission granting rights for Office, but as far as I could tell, once you follow the instructions to [install Assist for Teams](https://plz.halp.com/article/x359vientt-install-assist-for-teams) and [set up a queue in Teams](https://plz.halp.com/article/vhurd4fqz7-how-to-set-up-a-halp-queue-in-ms-teams), by navigating to that team and going to **Manage team** -\\> **Apps** and by **uninstalling** the Assist app from the team, this team won't be considered as Triage or Request team anymore. After that, you can repeat the steps to set up a queue to the same or some other team where, during the setup, you'll be asked if you want to use that team as a Request or Triage team.\n\nI'm not 100% sure that will work as I cannot test it on our site, but that's my best bet it will work.\n"
},
{
"author": "Nadim Mouawad",
"body": "is there a possible way to filter the request types and show certain requests in corresponding slack channels?\n"
}
]
}
]
| https://community.atlassian.com/t5/Assist-questions/How-to-change-the-Triage-Channel/qaq-p/1959583 | [
"triage"
]
|
{
"author": "phil.harder",
"title": "Newbie Question - Can't Find Halp App for Teams",
"body": "I'm a newbie at Teams apps. I'm attempting to add Halp and give permission to a test group. I'm following these instructions <https://plz.halp.com/article/x359vientt-getting-started> but I'm having trouble at step 1. Searching for the 'Halp' app finds nothing, but I can search for and find many other apps.\n\nWhat am I missing?\n"
} | [
{
"author": "Brian Feldman",
"body": "Halp's apps for MS Teams and Slack are being [renamed to Assist](https://community.atlassian.com/t5/Halp-articles/Meet-Atlassian-Assist-Halp-s-new-partner-in-crime/ba-p/1954001), so that update might have already rolled out for you, as it will for everyone over the next few days. \n\nIf you believe you already have authorization (as [@marcus.burnap](/t5/user/viewprofilepage/user-id/4098977) mentioned above), then try searching for **Assist** to see if results appear under that name.\n\n![Screen Shot 2022-03-02 at 11.04.42 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/186077iF71E0E9FD4C60568/image-size/large?v=v2&px=999 \"Screen Shot 2022-03-02 at 11.04.42 AM.png\")\n",
"comments": null
},
{
"author": "marcus.burnap",
"body": "Your 365 global or Teams admin will need to allow and authorize the app,\n\nIt will then be available to add to your Teams.\n",
"comments": [
{
"author": "phil.harder",
"body": "I am the global admin. :)\n\nCould it be because it is now called Assist?!\n"
},
{
"author": "Brian Feldman",
"body": "Hey [@phil.harder](/t5/user/viewprofilepage/user-id/4785568) , yes that could definitely be the case. Try searching for **Assist**. This update began rolling out across MSFT's servers yesterday, and should reaching all users in the coming days.\n\n![Screen Shot 2022-03-02 at 11.04.42 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/186079iC51C888127FD7A31/image-size/large?v=v2&px=999 \"Screen Shot 2022-03-02 at 11.04.42 AM.png\")\n"
},
{
"author": "phil.harder",
"body": "Thanks [@Brian Feldman](/t5/user/viewprofilepage/user-id/4517994) , I should have caught that. Made the change and install proceeded flawlessly.\n"
}
]
}
]
| https://community.atlassian.com/t5/Assist-questions/Newbie-Question-Can-t-Find-Halp-App-for-Teams/qaq-p/1960256 | [
"assist",
"ms-teams"
]
|
{
"author": "Bruce Anderson [Administrator]",
"title": "How to modify forms",
"body": "While we are able to modify and create fields, I see now way to be able to modify the default form, or create a new one. Can anyone explain what I am missing?\n"
} | [
{
"author": "Tomislav Tobijas",
"body": "Hi Bruce,\n\nForms are 'connected' to Assist Queues.\n\nIf you navigate to Assist **Settings ? Forms**, this page will just show a list of all existing forms that are connected to queues.\n\nTo edit existing or create a new form, go to **Settings ? Queues** . Now open a queue (just click to queue name) to which you want to add a form. Then, in the left navigation pane click on **Forms** and you'll be able to create new forms for that queue or edit existing one(s).\n",
"comments": [
{
"author": "Fletcher Richman",
"body": "Yup! To add a bit more detail here - Halp has the concept of Queues, which are basically the service desks for different teams at your company (IT Queue, HR Queue, etc).\n\nConfiguration for things like forms, fields, and statuses is on a queue by queue basis. So each Queue has a default form, and a set of Slack/Teams channels that are connected to that Queue. You can go into the Queue and edit the default form for that Queue, as well as add new forms and choose to have those forms be required or not for the channels connected to that Queue.\n"
}
]
},
{
"author": "Mark Koekemoer",
"body": "I am trying to modify the form for issues submitted via Slack, on linked Jira queues.\n\nI can't find the \"Assist\" platform in our Jira workspace, I only have the Halp platform. And in Halp, there is no option to edit a form - see attached. What am I missing? Where do I edit forms in Jira for linked queues?\n\nI want to be able to modify the form presented to a user in Slack when they create a ticket.\n\n![CleanShot 2023-03-13 at 15.34.09.png](https://community.atlassian.com/t5/image/serverpage/image-id/245261i73B3D61CBEAFB465/image-size/large?v=v2&px=999 \"CleanShot 2023-03-13 at 15.34.09.png\")\n",
"comments": [
{
"author": "Tomislav Tobijas",
"body": "Hi Mark,\n\nI think that once you connect Jira with Halp, a form that opens up in Slack is actually Create issue screen in Jira. From what I know, you cannot create custom forms in Halp if you're using Halp - Jira sync.\n\nSo, to modify the form that Slack user sees when opening a new ticket, you'll have to modify the Create issue screen that's actually opening this new Jira issue.\n\nNote - I think that was how it used to work like year or so ago. I'm currently setting up new integration between Halp and Jira (as I've switched companies since then), so I can test/confirm this as soon as the integration is ready for testing.\n\n**Update** - confirming that form visible in Slack is actually Create issue screen in Jira. In fact, when you're connecting Jira project to a queue, you'll get a warning popup saying that some items can only be configured in Jira.\n\n![Halp_integration_warning.png](https://community.atlassian.com/t5/image/serverpage/image-id/245671i1BAA4EEE3F0E90C3/image-dimensions/435x319?v=v2 \"Halp_integration_warning.png\")\n\nAdditionally, some Jira fields might not be supported in Halp and you'll see the list of those fields after you click **Continue** in previous popup.![connection_results.png](https://community.atlassian.com/t5/image/serverpage/image-id/245672i07097ED5871566BD/image-dimensions/435x470?v=v2 \"connection_results.png\")\n"
}
]
}
]
| https://community.atlassian.com/t5/Assist-questions/How-to-modify-forms/qaq-p/1959591 | [
"forms"
]
|
{
"author": "Eden",
"title": "How can I add value to an exist field, but only for 1 specific project?",
"body": "Hi,\n\nI want to add value to an exist field, but I want the change will be only for 1 project.\n\nThanks in advance\n"
} | [
{
"author": "Nic Brough -Adaptavist-",
"body": "Edit the issue you want to put the data into.\n\nOr, if you need to hit many issues, run a search for \"project = X\" and use bulk-edit to set the field on all the issues in the project.\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Assist-questions/How-can-I-add-value-to-an-exist-field-but-only-for-1-specific/qaq-p/1950058 | null |
{
"author": "Gnana Sundaram Kattapomman",
"title": "is possible to log a ticket by using Halp on Mobile Teams",
"body": "is possible to log a ticket by using Halp on Mobile Teams\n"
} | [
{
"author": "Tori Stitt",
"body": "Hi [@Gnana Sundaram Kattapomman](/t5/user/viewprofilepage/user-id/4747722) - Yes, Halp is designed to work on MS Teams mobile as well.\n\nTori\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Assist-questions/is-possible-to-log-a-ticket-by-using-Halp-on-Mobile-Teams/qaq-p/1937115 | null |
{
"author": "Gnana Sundaram Kattapomman",
"title": "Tickets created in Teams Halp will be stored in cloud?",
"body": "If we subscribe Halp on Teams, tickets will be stored in cloud? \nSame in Microsoft itself? \n\nWe are using Jira on premises\n\nPlease clarify.\n\nThanks\n"
} | [
{
"author": "Tori Stitt",
"body": "Hey [@Gnana Sundaram Kattapomman](/t5/user/viewprofilepage/user-id/4747722) Halp will sync tickets between Jira and MS Teams. Therefore, ticket details will be stored in Halp (which lives in Atlassian's cloud), as well as on MS Teams.\n\nHope this helps!\n\nTori\n",
"comments": [
{
"author": "Gnana Sundaram Kattapomman",
"body": "Thanks Tori.\n\nAlready we are using Jira - Agile on premises. same like jira, is possible to store ticket in our database? not in cloud. Please clarify\n"
},
{
"author": "Fletcher Richman",
"body": "Hey [@Gnana Sundaram Kattapomman](/t5/user/viewprofilepage/user-id/4747722) - it is not possible to store tickets directly in your database, all messages will be synced with Microsoft Teams and therefore will be in the cloud.\n"
},
{
"author": "Fletcher Richman",
"body": "We take our security seriously and to ensure your data is safe, for more see <https://www.atlassian.com/software/halp/security>\n"
},
{
"author": "Gnana Sundaram Kattapomman",
"body": "in ATLASSIAN cloud? (all messages will be synced with Microsoft Teams and therefore will be in the cloud)\n"
},
{
"author": "Fletcher Richman",
"body": "They will be in both the Atlassian Cloud as well as the Microsoft Cloud.\n"
},
{
"author": "Gnana Sundaram Kattapomman",
"body": "Thanks \nIs possible to synch the tickets with Microsoft Planner?\n"
},
{
"author": "Fletcher Richman",
"body": "That's not currently a feature we have but I can add it as a feature request for you!\n"
},
{
"author": "Gnana Sundaram Kattapomman",
"body": "Thanks Fletcher\n"
}
]
}
]
| https://community.atlassian.com/t5/Assist-questions/Tickets-created-in-Teams-Halp-will-be-stored-in-cloud/qaq-p/1937057 | [
"ms-teams"
]
|
{
"author": "Maxwell Warren Cudlitz",
"title": "read data from halp form using Slack API / Bolt",
"body": "I am attempting to create a bot which interacts with Halp generated tickets in a triage queue. \n\nI failed to see any way to make a custom integration or to make Halp directly send the form data to an external endpoint, so I am attempting to read form data from the message Halp sends in our triage channel. \n\nWhen I attempt to read this data from the message though, I see that the data is not directly in the message body or anywhere else.\n\n<https://pastebin.com/UyUVBYiF> \n\nthe form will load in Slack after the 'expand' button is pressed, but I do not see a way to get this data through Bolt nor the Slack API.\n\n<https://pastebin.com/kqtLyi3h>\n\nIn the message object, expanding attchments.actions, the data for the button can be accessed, but again, I do not see a way to call this button. \n\n<br />\n\nAny help on this topic would be appreciated, including if there is a way to create an integration that I have overlooked. \n\nThanks!\n"
} | [
{
"author": "Carlos Garcia Navarro",
"body": "Hi [@Maxwell Warren Cudlitz](/t5/user/viewprofilepage/user-id/4577002) ,\n\nI'm not sure how to accomplish what you're asking, but if you're still looking into it, I'd recommend to ask in the Atlassian Developer Community: <https://community.developer.atlassian.com/>\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Assist-questions/read-data-from-halp-form-using-Slack-API-Bolt/qaq-p/1819234 | null |
{
"author": "Sarah Nadif",
"title": "Jira service portal knowledge basearticles through Halp",
"body": "Is it possible to suggest knowledge base articles through Halp when someone creates a ticket in MS teams the same way KBs are suggested in Jira service portal?\n"
} | [
{
"author": "Tori Stitt",
"body": "Hi [@Sarah Nadif](/t5/user/viewprofilepage/user-id/3105626) ? - Yes, it will be possible this fall with Halp Answers in MS Teams! The feature enables you to connect your KB articles to Halp and then uses machine learning to suggest your KB articles based on the keyword terms presented in the request. When it goes live we will be notifying all of our current users and making an announcement in the community.\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Assist-questions/Jira-service-portal-knowledge-basearticles-through-Halp/qaq-p/1679240 | null |
{
"author": "Jens Kisters //SeibertSolutions",
"title": "Slack Community?",
"body": "Hi,\n\na little offtopic:\n\nWhere can i ask questions about Slack?\n\nslackcommunity.com seems to be only about events and not about online exchange (like atlassian community)\n\nThe AC doesnt have a Slack section either.\n\nThanks!\n\nJens\n\nP.S.: \nWhat i wanna post there is this: \n\nChallenge for **#nerds** :\n\nIm looking for a \\*lightweight\\* **#taskmanagement** solution that fullfills the following requirements:\n\n# email integration (create new tasks via email)\n\n# slack integration (create tasks right out of slack)\n\n# tells me on a regular basis which tasks are still open. It needs to nag me. never grows tired of nagging me till its **#done**\n"
} | [
{
"author": "Jens Kisters //SeibertSolutions",
"body": "in the meantime i learned that there is slack community, but in opposition to what im used to from the Atlassian Ecosystem its not web-based, its a [slack workspace](https://community.slack.com/x-p548674484641-2563616029911-2570571562359/) (what a surprise) that is not as easy to find as it would be optimal.\n",
"comments": null
},
{
"author": "Tori Stitt",
"body": "do you mean [Halp](https://www.atlassian.com/software/halp/slack-ticketing)?\n",
"comments": [
{
"author": "Jens Kisters //SeibertSolutions",
"body": "no, i mean independent from halp.\n"
}
]
}
]
| https://community.atlassian.com/t5/Assist-questions/Slack-Community/qaq-p/1828020 | null |
{
"author": "serge calderara",
"title": "HALP integration with Jira Service Desk failed on Assignee field",
"body": "Dear all,\n\nWe are testing the integration of HALP through SLAck in order to be able to create ticket in Service Desk directly from slack message.\n\nWe have run different test so far and we face a wierd issue with Assignee and Reporter field.\n\n1. When we create a ticket from slack, HALP does not update correctly he Reporter field which is suppose to be the user who create the ticket\n2. When we assigned the ticket to a user in Slack, HAlp doe not update the Assignee field in Jira.\n\nDoes any of you face the same thing with this integration and could share ?\n\nregards\n"
} | [
{
"author": "Tori Stitt",
"body": "[@serge calderara](/t5/user/viewprofilepage/user-id/3385932) - can you provide more detail as to what issue you might be having? Or have you been in contact with our support team?\n\nLet me know how I can halp out or point you in the right direction.\n",
"comments": null
},
{
"author": "Gonchik Tsymzhitov",
"body": "[@serge calderara](/t5/user/viewprofilepage/user-id/3385932) welcome to the community.\n\ndid you find some option ?\n\nJust looking into product and interesting to understand the situation of usage\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Assist-questions/HALP-integration-with-Jira-Service-Desk-failed-on-Assignee-field/qaq-p/1541203 | [
"jira-service-management",
"jira-service-management-server",
"server"
]
|
{
"author": "Marissa Moroz",
"title": "Getting error when trying to re enable publishing on Jira Product Discovery",
"body": "We have been using shared views on Jira Product Discovery and users are not reporting they cannot access the board. I tried to disable and re enable the publishing but now I am getting an error and cannot turn back on.\n\nIt just says failed to enable views publishing ![Screenshot 2024-08-06 at 8.23.34?PM.png](/t5/image/serverpage/image-id/340405iE7848177367D3DC0/image-size/large?v=v2&px=999 \"Screenshot 2024-08-06 at 8.23.34?PM.png\")\n"
} | [
{
"author": "Nick H",
"body": "Hi [@Marissa Moroz](/t5/user/viewprofilepage/user-id/2014658) ,\n\nAre you by chance using SSO? Customers recently reported some issues publishing views with stakeholders who had **not** signed up for an Atlassian account, and SSO was enabled in their JPD.\n\nIf not, it might be worth reaching out to [JPD support](https://support.atlassian.com/contact/#/) for additional assistance to troubleshoot this issue.\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Getting-error-when-trying-to-re-enable-publishing-on-Jira/qaq-p/2777565 | [
"cloud",
"jira",
"jira-cloud"
]
|
{
"author": "Simon Pentzien",
"title": "Epics in Jira Product Discovery",
"body": "Hi there, how do you handle the challenge that in Jira Product Discovery you cannot differentiate between Epics and tasks/subtasks, but only create either epics or tasks when you \"transfer\" an item from Jira Product Discovery to standard Jira\n"
} | [
{
"author": "Nick H",
"body": "Hi [@Simon Pentzien](/t5/user/viewprofilepage/user-id/5492585) ,\n\nI believe when a JPD idea [creates a Jira delivery](https://support.atlassian.com/jira-product-discovery/docs/create-a-jira-issue-from-jira-product-discovery/), you can select any of the available of [issue types](https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-types/) under the Jira project selected (Epic, Task, Bug, etc.).\n\nBut I don't believe it's possible to create a subtask or child issue from a JPD idea since these are managed through the issue **after** the Jira issue is created.\n\nNot sure if that helps so if you can clarify the issue a bit more, or how you are hoping to handle the challenge, it might help with providing additional information.\n",
"comments": [
{
"author": "Simon Pentzien",
"body": "Hi Nick, yes, this helps a lot, thanks for clarifying\n"
}
]
},
{
"author": "duncan_crowell",
"body": "I think what you are asking here I went through the same level of thinking. There has been some discussion on here around a Hierarchy in JPD to help you to manage different size Ideas but for now at least I have just rationalised this by using description and Labels for the different sized ideas.\n\nFor example if I have a large Initiative (or Epic) Idea I will label it with \"Epic\" and put \\[Epic\\] in the Idea summary for visual scanning purposes. WHen it comes time to transfer this to Jira I simply create the multiple features associated with the Idea for Release 1 (or MVP) so that from with JPD I can then see the several features that make up that epic.\n\nWhere required I then create any other features not part of MVP associated with that Epic as a new Idea in JPD and tag them as \"Feature\" with \\[Feature\\] in the Idea summary. And that feature goes through Discovery at the feature level.\n\nIts not pretty but it works for now until the team figure out a clear way to do a hierarchy.\n",
"comments": [
{
"author": "Simon Pentzien",
"body": "Awesome, we will try to do the same, sounds like a pragmatic workaround. thank you!\n"
}
]
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Epics-in-Jira-Product-Discovery/qaq-p/2777120 | null |
{
"author": "slmorton",
"title": "How do I allow everyone in my organisation to create an idea, but limit the views they can see?",
"body": "I really want everyone in my organisation to be able to create an idea, add comments and insights etc but I don't want them to have access to every view in the system.\n\nTo my mind the Stakeholder approach makes sense, for limiting the views . . . but how can I allow team members not in JPD to create an idea?\n\nDoes JPD support anyway of having a more open portal for gathering ideas from the wider organisation?\n\nThe Contributor role will allow idea creation but, honestly, I don't want sales/marketing, CS or consultancy seeing all the views, that will end in chaos.\n"
} | [
{
"author": "Hermance NDounga",
"body": "Hi there,\n\nExactly what Gary said, we are coming up with a view permission feature so you will be able to hide some views from contributors (or any user).\n\nWe are also considering improving the stakeholder view, but it is not currently planned on our roadmap.\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n",
"comments": null
},
{
"author": "Gary Spross",
"body": "[@slmorton](/t5/user/viewprofilepage/user-id/3463131), Atlassian has an [EAP for the JPD Premium version](https://www.atlassian.com/software/jira/product-discovery/premium). This is the version that will include \"View Permissions\". I'm not sure what that means exactly, but I'm imagining something like your describing.\n\nThe main issue is obviously that this will be a feature available only in the Premium version, so if you don't foresee a need for any of the other features in that version, it'd be very costly to upgrade for just this single feature addition.\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/How-do-I-allow-everyone-in-my-organisation-to-create-an-idea-but/qaq-p/2776629 | null |
{
"author": "Ravid",
"title": "Tricky / Misleading in \"Add user\" to Jira Product Discovery",
"body": "When adding a new user, Jira Product Discovery is automatically set to a new user. \nWe need to set it manually to \"not a user\" as long as JPD is not widespreaded, otherwise we need to pay extra licences. Would be really nice if you could change that, dear Product Manager of JPD. Pls! \n![Bild (4).png](https://community.atlassian.com/t5/image/serverpage/image-id/339987i9994BD6D3DD65CF0/image-size/large?v=v2&px=999 \"Bild (4).png\")\n"
} | [
{
"author": "Hermance NDounga",
"body": "Hi Ravid,\n\nBy default, a new user is counted as a user for all product on the site, we cannot change this behaviour just for Jira Product Discovery. Also it might be different for each company, some would need to have this behaviour for Confluence and some other for Bitbucket.\n\nSo in that case, I think it would be a good feature request for the platform team: being able to decide which products you'd like to provision by default on your site: <https://community.atlassian.com/t5/Atlassian-Platform/ct-p/platform>\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Tricky-Misleading-in-quot-Add-user-quot-to-Jira-Product/qaq-p/2775522 | null |
{
"author": "Phillip Jones",
"title": "Automation to fill in resources etc",
"body": "So we are probably using JPD in the wrong way, but since plans doesn't support multiuser pickers (for some reason), I'm trying to get our project valuation list into JPD so my leadership stops using an excel sheet. \nI have JPD setup very nicely right now and I'm hoping I can put a bow on it with some automations and one of the biggest automation requests is to automatically pull the users from linked issues (an epic or initiative etc) and take the users listed under additional participants and them pipe them to JPD and add them to the resources field. \n\nHowever, I'm running into not being able to find that field in automations. \n\nDoes anyone know if there is a way around this? If I had a custom field ID this would be about as standard as ever but I'm not sure how or where the \"fields\" in JPD are store and how to reference them. I'm willing to do API calls if needed as well but unsure of how I may even be able to do that. \n\nEDIT: Just to update, I ran a get on the issue from JPD and was able to find the custom field value, it just looks like I'll have to configure the advanced field editing. If anyone has any advice for that too, I'm all open. Right now I have to play this game of cat and mouse on how to trigger it properly and then not getting a correct JSON unfortunately.\n"
} | [
{
"author": "Nick H",
"body": "Hi [@Phillip Jones](/t5/user/viewprofilepage/user-id/5193482) ,\n\nWhat [@Gary Spross](/t5/user/viewprofilepage/user-id/5166286) shared should help. You can use an automation / JSON body like in that post, or below to map Jira delivery people-fields to JPD idea people-fields:\n\n![auto23.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/340099i21214D0B1675F8E8/image-size/large?v=v2&px=999 \"auto23.jpeg\")\n\n```\n{\n\"fields\": {\n\"customfield_JPD\": [ { \"accountId\": \"{{triggerIssue.customfield_JIRA.accountId}}\" } ]\n}\n}\n```\n\n\\^ Having said that, this has only been able to work as expected mapping a Jira people-field to a JPD people-field when **one** user is selected.\n\nI have not been able to get this working with a multiple user picker field / multiple users configured in the Jira field. I'll continue testing and hopefully will have something soon.\n",
"comments": [
{
"author": "Phillip Jones",
"body": "Thank you for the help! I've gotten this far for sure and the logs are showing IDs, it also shows as a successful run but I've noticed 2 things. \n\n1. Even though a success, it doesn't actually add them (I'm testing with a ticket with 2 users because many have more than 1. \n\n2. This is the more concerning one, I am noticing, if I change the ticket in the \"Linked Ticket\" field in JPD (which is what I have the trigger set to) it keeps pulling the info from another ticket. I'm using the\n\n```\n{{triggerIssue.customfield_JIRA.accountId}}\n```\n\nsmart value that you suggested but it was happening before as well when I was using \n{{issue.issuelinks.inwardIssue.customfield_XXXXX}} \n\nNot sure why it's not picking the right ticket for the IDs. That's also secondary to it not actually setting them as well.\n"
}
]
},
{
"author": "Gary Spross",
"body": "[@Phillip Jones](/t5/user/viewprofilepage/user-id/5193482), the answer to this question may help guide you.\n\n<https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Copy-value-of-the-reporter-creator-field-into-a-custom-people/qaq-p/2726412>\n",
"comments": [
{
"author": "Phillip Jones",
"body": "Yes, I've gotten pretty far right now but running into a weird error. \n\nI think my logic might be wrong? The logs show the IDs correctly so it's seeing them it's just failing to add them for some reason.\n\nNow I'm seeing in the logs \"Pick another user as the selected user doesn't exist.\" \n![JPD Automation issue 1.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/340098i643B229C9E957FAA/image-size/large?v=v2&px=999 \"JPD Automation issue 1.PNG\") \n![JPD Automation issue 2.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/340096i02572FCD64A00ADE/image-size/large?v=v2&px=999 \"JPD Automation issue 2.PNG\") \n"
}
]
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Automation-to-fill-in-resources-etc/qaq-p/2775856 | [
"jira-cloud",
"jira-product-discovery"
]
|
{
"author": "Antal Vig Communardo",
"title": "Team field in JPD",
"body": "(Sorry if this isn't in the Jira Product Discovery Questions, seem I can't ask Q's to my JPD) \n\nHi folks, I tired to use the Atlassian Team fields to \"assign\" delivery tickets to Teams, but It seems they are not availble. \nNeither as JPD Fields, nor as normal Jira Fields within JPD. And I even went as far as trying if they are working in the assignee field, but no chance. \nDo you guys have any plan on Implementing those, or will you stick to the dropdown as it is in the default project? \nThanks\n\nAntal\n"
} | [
{
"author": "Hermance NDounga",
"body": "Hi Antal,\n\nAtlassian teams are not yet available in Jira Product Discovery :( but we will be working on it before the end of the year. Stay tuned here to get the update.\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Team-field-in-JPD/qaq-p/2775498 | [
"cloud",
"jira",
"jira-cloud"
]
|
{
"author": "Kshitij Raval",
"title": "Jira Product Discovery - Project Settings",
"body": "Hi,\n\nRecently we have started using Jira Product Discovery. I have \"creator\" access, however I do not see \"Project Settings\" menu option on the left pane. What settings/steps/access do I need to see \"Project Settings\".\n\nFor the Jira Product Discovery project, I want to do is:\n\n1. Change the project name\n\n2. Add few new fields\n\n3. Give view access to everyone on the team\n\nThanks\n\nKshitij Raval\n"
} | [
{
"author": "lila",
"body": "Hey Kshitij, you need to be an admin also to be able to do that. You might want to check with your jira admin to make you and admin on that project to be able to see the panel and make the amends you are after.\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Jira-Product-Discovery-Project-Settings/qaq-p/2775421 | [
"cloud",
"jira",
"jira-cloud",
"jira-product-discovery"
]
|
{
"author": "Yuliia Vyborova",
"title": "Automation that populates field value from JPR to Jira",
"body": "Hello! \nI need automation that populates field value SPR or IPR to Jira ticket that linked as 'is delivered' to JPD idea. I set the following automation and log says Success but there are no change in Jira ticket.\n\nPlease see steps I set:\n\n![Screenshot 2024-08-02 at 9.57.34?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/339782i5880955405293233/image-size/large?v=v2&px=999 \"Screenshot 2024-08-02 at 9.57.34?PM.png\")![Screenshot 2024-08-02 at 9.57.44?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/339783i5A0E6A19F2742C27/image-size/large?v=v2&px=999 \"Screenshot 2024-08-02 at 9.57.44?PM.png\")\n\nAudit log says Sucess![Screenshot 2024-08-02 at 10.20.53?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/339784i13FA820B3BC49807/image-size/large?v=v2&px=999 \"Screenshot 2024-08-02 at 10.20.53?PM.png\")\n\nBut Jira ticket (2nd picture) that is linked as 'is delivered by' to Idea has empty value, however I se SPR value in JPD (1st picture)\n\n![Screenshot 2024-08-02 at 10.21.49?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/339785i5E04862A44C88446/image-size/large?v=v2&px=999 \"Screenshot 2024-08-02 at 10.21.49?PM.png\")![Screenshot 2024-08-02 at 10.22.11?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/339786i67EAB95BFE74A297/image-size/large?v=v2&px=999 \"Screenshot 2024-08-02 at 10.22.11?PM.png\")\n\nWhat I missed in automation rule?\n"
} | [
{
"author": "Nick H",
"body": "Hi [@Yuliia Vyborova](/t5/user/viewprofilepage/user-id/3597151) ,\n\nCan you share the THEN component of your automation?\n\nI believe you will want to **Copy from Trigger issue** if you do not have this selected.\n\nIt's also typically best practice to map to the same field-types, otherwise there may be some unexpected behavior.\n\nIt appears the \"SPR or IPR\" may be a single select option. Important to note that this option needs to be available within the \"SPR or IPR item?\" field's options. Automations do not have the ability to create new options, so they need to exist in order for the automation to work as expected.\n",
"comments": [
{
"author": "Yuliia Vyborova",
"body": "[@Nick H](/t5/user/viewprofilepage/user-id/2540930) Sorry for delay, I was on vacation.\n\nI just checked that SPR or IPR item and SPR or IPR? have the same field type and options. So it should populate values properly. Also, I am attaching THEN action\n\n![Screenshot 2024-08-14 at 6.59.19?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/341819i745F6A45AF954648/image-size/large?v=v2&px=999 \"Screenshot 2024-08-14 at 6.59.19?PM.png\")\n"
},
{
"author": "Yuliia Vyborova",
"body": "[@Nick H](/t5/user/viewprofilepage/user-id/2540930) also, I wonder what is the best way to keep both Idea and delivery tickets aligned? I see the potential issue with updating one field in Idea and need to update field on delivery ticket - that sounds like a not consistent way to do and also not scalabel so I appreciate any ideas here.\n"
},
{
"author": "Nick H",
"body": "Hi [@Yuliia Vyborova](/t5/user/viewprofilepage/user-id/3597151) ,\n\nYou should be copying from the **Trigger issue** in the THEN condition, and not the Current issue for this type of automation.\n\nAs for keeping both idea and delivery tickets aligned, you would need an automation designated for both directions - or realistically:\n\n1. When delivery is created, map idea fields to delivery fields\n2. (After delivery created) When delivery field(s) updated, update idea field(s)\n3. (After delivery created) When idea field(s) updated, update delivery field(s)\n\nWe understand this isn't exactly scalable especially if there are lots of fields you want to keep aligned, but at this time it's only possible to update ideas \\<-\\> deliveries through automations.\n"
},
{
"author": "Yuliia Vyborova",
"body": "Got it, thank you [@Nick H](/t5/user/viewprofilepage/user-id/2540930) ! I adjusted THEN step and automation works now!\n"
}
]
},
{
"author": "Hermance NDounga",
"body": "Hey Yuulia,\n\nWe have created templates in global automation that let you bring info from the idea to the delivery ticket. Can you use the first global template as the base for your rule? making incremental changes to the template so you reach what you're looking for\n\n<https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Introducing-new-automation-templates-for-Jira-Product-Discovery/ba-p/2504036>\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n",
"comments": [
{
"author": "Yuliia Vyborova",
"body": "thanks a lot [@Hermance NDounga](/t5/user/viewprofilepage/user-id/430755) ! I will explore the article\n"
}
]
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Automation-that-populates-field-value-from-JPR-to-Jira/qaq-p/2774534 | null |
{
"author": "Martin",
"title": "Creating a delivery ticket: automation to append the summary",
"body": "Good day,\n\nI am familiar with automation. I am creating a new JPD project and new JS projects for a new team.\n\nWhen creating an EPIC as a Delivery Ticket, I want to append the name automatically and insert the ID of the JPD ticket.\n\nI know I have to use the JSON configuration, but so far, I can only append using the EPIC key, but I need the key of it's parent (polaris). Any idea?\n"
} | [
{
"author": "Hermance NDounga",
"body": "Hello Martin,\n\nI'm not sure why you'd need to use JSO for this.\n\nYou can start from the two template that have been created for Jira Product Discovery and that can be found under global automation to see how you can flow data from the idea to the epic.\n\nWhere do you want to include the ID of the JPD ticket (or for which reason)?\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n",
"comments": [
{
"author": "Martin",
"body": "Hi Hermance,\n\nWhen the portfolio team creates an Epic (Delivery Ticket), they want to always have the ID of the JPD idea in the name. For sure, we can do it manually, but we want to automate it. So the rule is, when created, rename the ''summary'' with the Summary + idea Key.\n\nI'll check the templates.\n"
}
]
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Creating-a-delivery-ticket-automation-to-append-the-summary/qaq-p/2774330 | null |
{
"author": "Christian Happel",
"title": "Embed Jira Product Discovery idea collection into any website",
"body": "Hi,\n\nwhy isn't it possible to create an issue collector in Product Discovery, in the same way you can do it for regular Jira projects? \nThis way I could embed this directly into our product and let discovers submit their own ideas directly into a JPD project.\n"
} | [
{
"author": "Hermance NDounga",
"body": "Hello Christian,\n\nJira Product Discovery has been tought as a product for product manager and help them create a curated product backlog. In that sense, it has not been designed so anyone can raise any idea, not being aware of any of the rest of the idea you already have in the backlog, or not knowing anything about company goals etc..\n\nThat's why at the beginning, only licensed users (usually, Product Managers) had the the possibility to create ideas - to make sure the list of ideas is clean, manageable, easily understandable by product stakeholders, etc.\n\nThen thanks to our customer feedback we realized Product Managers wanted to have other functions to be able to add ideas - specifically roles that are customer facing: Sales teams, support engineers etc. And that's why we introduced the contributor role, and let unlicensed users to create ideas. But still they can read other ideas, avoid duplications, are aware of the company goals etc..\n\nAnd with the time, we received some feedback from customer that they would like to have all their customer being able to create ideas. \nAs the Jira Product Discovery team, we are using Jira Product Discovery and we do use Jira Service Management to achieve this. Everyday we receive dozens of new ideas, and we prefer to keep them in Jira Service Management until we are able to correctly classify them and attach them correctly to the existing idea - keeping our Jira Product Discovery project clean where we can prioritize based on criteria and build a product roadmap, and not just another place where feedback comes to die.\n\nOur head of product explains [this well in this webinar (check min 19).](https://www.youtube.com/watch?v=Yp0q7YVYM4c)\n\nHowever, with the introduction of the stakeholder role, we are revisiting this opinion and we might change it ;) but you have the (long) reason why there are no issue collectors in Jira Product Discovery at the moment, and if we would introduce something similar, we would still want to make sure that Jira Product Discovery remains the place where PMs can build their product roadmap and not a feedback collector tool.\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n",
"comments": [
{
"author": "Christian Happel",
"body": "Thanks Hermance for the explanation!\n\nWe are using Jira Service mgmt already for support tickets as well. \nI'm still looking for an easy way for customers to submit ideas, see other customers' ideas and vote for them, and then manage them downstream in a roadmap (Jira plans for us) and a backlog within a dedicated development team. \nJPD seems to be one of the puzzle pieces in this scenario, but not fully integrated yet. I'm actively monitoring what you will come up with in the future.\n\nI also only realized last week that it was possible to just embed a collector of any development Jira project into a website.\n"
}
]
},
{
"author": "Jens Schumacher - Released_so",
"body": "[@Christian Happel](/t5/user/viewprofilepage/user-id/4910998) would love to have a chat. We are exploring how we might be able to make this process simpler. Feel free to get in touch directly via jens at released.so\n",
"comments": null
},
{
"author": "?ukasz Modzelewski _TTPSC_",
"body": "Maybe it relates to the fact that in JPD licensing is based on creators - who can create new ideas.\n\nMaybe this can be covered by some JSM portal, then add some layer of approval of idea then some automation to change the reporter/creator and creating it in JPD with JSM ticket as 1 of insight? \\^\\^\n",
"comments": [
{
"author": "Christian Happel",
"body": "Yeah, maybe.\n\nAn automation would be possible of course, but it's so complicated while it could be so simple.\n"
},
{
"author": "?ukasz Modzelewski _TTPSC_",
"body": "Here is a great (\\& fresh) example from [@Axel Sooriah](/t5/user/viewprofilepage/user-id/5400521) : <https://community.atlassian.com/t5/Jira-Product-Discovery-articles/How-to-Creating-an-idea-intake-process-with-JPD-and-JSM/ba-p/2777882#U2777914>\n"
}
]
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Embed-Jira-Product-Discovery-idea-collection-into-any-website/qaq-p/2775232 | [
"cloud",
"jira",
"jira-cloud"
]
|
{
"author": "Mia Maric",
"title": "Watching widget in Jira Product Discovery",
"body": "Is there a widget or metric that can be used in Jira Product Discovery to view the ideas someone is \"watching\"?\n\nSome of my stakeholders may only be interested in tracking a few ideas rather than seeing them all.\n"
} | [
{
"author": "lila",
"body": "A way of doing this would be to create a field \"watcher\" and then create a specific view for them where you **filter** or **group by** your issues by \"watcher.\"\n",
"comments": [
{
"author": "Mia Maric",
"body": "Creating a field would mean that folks would have to go in and tag themselves as a watcher. It's not a clean workaround but I guess it could do until a widget is created in JPD, like they have in Jira Software.\n"
}
]
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Watching-widget-in-Jira-Product-Discovery/qaq-p/2774204 | [
"cloud",
"jira",
"jira-cloud",
"jira-product-discovery"
]
|
{
"author": "Jens Schumacher - Released_so",
"title": "JPD ideas not showing amongst recently viewed issues",
"body": "When trying to navigate to recently viewed JPD ideas, they don't seem to appear in the recently viewed list that appears when clicking the search bar. \n\nLooks like a bug?\n\n![Screenshot 2024-08-01 at 12.07.39.png](https://community.atlassian.com/t5/image/serverpage/image-id/339297iDB31AC78A1DBCE9C/image-size/large?v=v2&px=999 \"Screenshot 2024-08-01 at 12.07.39.png\")\n"
} | [
{
"author": "Hermance NDounga",
"body": "Hi Jens,\n\nWe aren't able to reproduce the issue - ideas are displayed amongst other jira ideas.\n\n![Screenshot 2024-08-01 at 19.37.41.png](https://community.atlassian.com/t5/image/serverpage/image-id/339532i77546851BE593555/image-size/large?v=v2&px=999 \"Screenshot 2024-08-01 at 19.37.41.png\")\n\nif you still have the problem, please raise a ticket using the give feedback button on the left side bar and include a screenrecording\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n",
"comments": [
{
"author": "Jens Schumacher",
"body": "It's still not working. Will raise it via Feedback.\n"
}
]
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/JPD-ideas-not-showing-amongst-recently-viewed-issues/qaq-p/2772320 | [
"bug"
]
|
{
"author": "Dan Horsfall",
"title": "Create issue automation failing with \"Please select a valid project\" instead of permission issue",
"body": "When creating a Jira automation to create an issue in a restricted JPD Project, I get the error attached - \"Please select a valid project\"![JPD fails with invalid.png](https://community.atlassian.com/t5/image/serverpage/image-id/339247i3A971AF8D9D235C0/image-size/large?v=v2&px=999 \"JPD fails with invalid.png\")\n\nAfter troubleshooting I found that this is because the project I was trying to create in was restricted. When I change the rule actor, or open the project up it seems to work. Feels like a bug that it didn't say \"You don't have permission to create issues in this project. You may be able to adjust those settings here ....\"\n\nAlso wanted to ask if there is a way to add the Automation for Jira user as a contributor to the JPD project? I don't see it in the user select. Do I need to create a specific bot user for this purpose?\n\nThanks!\n"
} | [
{
"author": "Nick H",
"body": "Hi [@Dan Horsfall](/t5/user/viewprofilepage/user-id/3944780) ,\n\nSorry for any inconvenience here. If I had to guess, it's probably an issue with the A4J user vs. the restriction of the project's Settings / Access.\n\nWe've noticed some customers' A4J user not being granted JPD permission. This isn't so much a bug, but something we're working on correcting.\n\nRegardless, 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 do that within JPD under the *Give Feedback* tab \\>\\> *Get help from the support team* , or [HERE](https://support.atlassian.com/contact/).\n",
"comments": [
{
"author": "Dan Horsfall",
"body": "Great, Thanks Nick!\n"
}
]
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Create-issue-automation-failing-with-quot-Please-select-a-valid/qaq-p/2772151 | null |
{
"author": "Ravid",
"title": "Product Discovery Crash Course",
"body": "Hi, \n\ndo you plan to offer an online course for Jira Product Discovery? \nDid not find any here: \n\n<https://www.atlassian.com/university>\n\nThanks!\n\nRavid\n"
} | [
{
"author": "Tanguy Crusson",
"body": "By the way [@Ravid](/t5/user/viewprofilepage/user-id/4927950) we've started working on a handbook to explain how you can adopt JPD for things like this.\n\nYou can find it here: [Jira Product Discovery handbook](https://pm-dev.atlassian.net/wiki/external/MDkxNmFkNWQ4Yzk1NDA5OGIxOWU0MmVkMmFmYjEwM2Q).\n",
"comments": null
},
{
"author": "Axel Sooriah",
"body": "Hi [@Ravid](/t5/user/viewprofilepage/user-id/4927950)\n\nthis is certainly something we are exploring.\n\nHere are a few resources you can dive into to learn more about how to best use JPD:\n\n* [A comprehensive Loom video demo of JPD](https://www.loom.com/share/ee4389d7b31c4fdf966ce29445590095?sid=d438c670-4699-40f3-9ed6-2328ca732792)\n* [The FAQ section here with even more videos and \"how-to\" content](https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Frequently-asked-questions-about-the-product-how-do-I/ba-p/2002378)\n\nHopefully this helps.\n\nDo reach out if you need help on anything specific.\n",
"comments": [
{
"author": "Antoni Abella Vendrell",
"body": "[@Axel Sooriah](/t5/user/viewprofilepage/user-id/5400521) , the video is not publicly available. I sent a request, but it might be nice to remove that restriction.\n"
},
{
"author": "Antoni Abella Vendrell",
"body": "Now I can access, thanks!!\n"
},
{
"author": "Axel Sooriah",
"body": "[@Antoni Abella Vendrell](/t5/user/viewprofilepage/user-id/5437101) Should be publicly available now. :)\n"
}
]
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Product-Discovery-Crash-Course/qaq-p/2773766 | null |
{
"author": "Zalak Patel",
"title": "Why do Ideas have multiple description fields?",
"body": "I see the description field 2 times, how do I eliminate one of them?\n\n![Screenshot 2024-07-29 at 1.17.53?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/339164iADF49B672A06489A/image-size/large?v=v2&px=999 \"Screenshot 2024-07-29 at 1.17.53?PM.png\")\n"
} | [
{
"author": "Nick H",
"body": "Hi [@Zalak Patel](/t5/user/viewprofilepage/user-id/5538692) ,\n\nCan't say I've ever seen that before, nor thought it be possible since you cannot name a JPD field after any system field.\n\nIt might be worth reviewing your JPD fields to see if there are two description fields, and editing the one that is not the system field.\n\nOtherwise feel free to open a ticket with the JPD support team under the *Give Feedback* tab \\>\\> *Get help from the support team* , or [HERE](https://support.atlassian.com/contact/).\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Why-do-Ideas-have-multiple-description-fields/qaq-p/2771812 | null |
{
"author": "Yuliia Vyborova",
"title": "JQL search for Linked issues in Idea tickets",
"body": "Hello! I am searching for ideas in JPD that have delivery ticket linked. But I can't find any issues however they exist.\n\n![Screenshot 2024-07-31 at 5.21.12?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/339149iBADE95D4EBEDDC21/image-size/large?v=v2&px=999 \"Screenshot 2024-07-31 at 5.21.12?PM.png\")\n\nAlso, I see 3 duplicate fields for Delivery status and Delivery progress (both from JPD I assume) and none of them seems searching.\n\nThis is my JQL:\n\n```\nissuetype = Idea and project = \"Product Discovery\" and cf[16455] is empty and cf[16576] is not EMPTY\n```\n\nplease see screenshot of those duplicate fields.![Screenshot 2024-07-31 at 5.17.03?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/339148iBDB47BE5FBA3CDE6/image-size/large?v=v2&px=999 \"Screenshot 2024-07-31 at 5.17.03?PM.png\")\n\nI tried in search all cf \\[16418\\]; cf \\[16444\\] and cf \\[16577\\] - to no evil.\n\nPlease advice how can I find Ideas that have delivery tickets in JQL!\n"
} | [
{
"author": "Nick H",
"body": "Hi [@Yuliia Vyborova](/t5/user/viewprofilepage/user-id/3597151) ,\n\nI would suggest using a JQL with something like this to determined which idea(s) have a delivery linked:\n\n```\nproject = XYZ AND issueLinkType = \"is implemented by\"\n```\n\nThe link type between idea to delivery is \"is implemented by\" so this would pull all ideas that have a delivery.\n\nWe're aware of the duplicate JPD fields such as Delivery progress, Delivery status, and a few others that appear in the Filters tab when JQL'ing. If you wanted to find the specific project's Delivery progress [field ID](https://confluence.atlassian.com/jirakb/how-to-find-any-custom-field-s-ids-744522503.html), below is a (not so pretty) method:\n\nAfter completing a general JQL such as on the JPD project, add a new column to the query and select **all** Delivery progress fields:\n\n![dp1.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/339204i11A33FCB1EF781EE/image-size/large?v=v2&px=999 \"dp1.jpeg\")\n\nFollowing that, the Delivery progress field that only applies in the filter would be the one that relates to the queried JPD project. The others would disappear.\n\nYou could then sort this column to determine the field's ID:\n\n![dp2.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/339205iB62ACBBD394184F4/image-size/large?v=v2&px=999 \"dp2.jpeg\")\n\nHaving said all that, it's **not** possible to query on the Delivery progress field in the Filters tab (at this time) since this field is not returned using the [API](https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#version) even if a delivery is linked to the idea. The field's values would also show blank in the Filters tab like in the above screenshot.\n\nSo the top / initial suggested JQL would be the best method in my opinion.\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/JQL-search-for-Linked-issues-in-Idea-tickets/qaq-p/2771782 | null |
{
"author": "Clayton",
"title": "Transitioned issue to Jira",
"body": "Hi\n\nIt seems when a create a ticket from JPD into a JIRA project it does not match the hierarchy which is defined in JIRA. Eg) in JIRA I have Initiative - Epic / story then when I create an initiative I can't create an epic as a child.\n\nis there anything you think I am doing wrong?\n\nthanks\n"
} | [
{
"author": "Hans Polder",
"body": "[@Clayton](/t5/user/viewprofilepage/user-id/4113287) ,\n\nCan you share a couple screenshots on how exactly you're trying to accomplish this?\n\nI just went to my test site, opened up the JPD project, went to the Delivery tab, clicked 'Create a delivery ticket', created an Initiative in my Test PFM project, then created a new Epic which I was able to link to my Initiative ticket as parent.\n\n![Screenshot 2024-07-31 115725.png](https://community.atlassian.com/t5/image/serverpage/image-id/339088i9CEA2ED83D324C24/image-size/large?v=v2&px=999 \"Screenshot 2024-07-31 115725.png\")\n",
"comments": [
{
"author": "Clayton",
"body": "Apologies I made a fundamental error.\n\nAppreciate it\n"
},
{
"author": "Hans Polder",
"body": "No problem! Happy to hear it's working now. For the rest of us, it might be good if you could share your 'fundamental error', so others know what to look for if they are in the same situation ;)\n"
},
{
"author": "Clayton",
"body": "Sorry [@Hans Polder](/t5/user/viewprofilepage/user-id/5506451) was on leave. My error was just me making a very silly mistake that I don't think anyone else will make :) \n\nI appreciate you taking the time to help.\n"
}
]
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Transitioned-issue-to-Jira/qaq-p/2771353 | null |
{
"author": "Gilad Waldman",
"title": "Polaris Datapoint Link Triggered automation",
"body": "Hello Community,\n\nWhile trying to trigger an automation upon Linked issues (Issue link type = Polaris datapoint), i fail to trigger the automation although adding insights into an idea.\n\nAs i struggle with this thing from the moment we migrated out product board into JPD, i understand that the JPD do not support insights automation yet - So this link type is not active and is planned to be?\n\nIs there a ticket i can track to see if a change is planned on insights automation? This could be a real game changer here.\n"
} | [
{
"author": "Hermance NDounga",
"body": "Hello Gilad,\n\ninsights is a Jira Product Discovery specific concept and isn't supported in Automations, you're not missing something.\n\nCould you please elaborate on what you're looking to achieve?\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n",
"comments": [
{
"author": "Gilad Waldman",
"body": "Sure [@Hermance NDounga](/t5/user/viewprofilepage/user-id/430755) , i can share an example\n\nWe capture most of our insights from Slack as we process support cases and feature requests (example attached)\n\n![Untitled.png](https://community.atlassian.com/t5/image/serverpage/image-id/339217iABF5DEB636925C81/image-size/large?v=v2&px=999 \"Untitled.png\")If automation was available, i could have parse the data to automatically extract customer name and add it to the idea and other relevant information into the idea\n\nI could also edit the format of the insight to present the data in a more organized way (Now it looks like a chunk of data and i wish to make it more readable)\n\nThanks.\n"
},
{
"author": "Hermance NDounga",
"body": "Hey Gilad,\n\nThanks a lot for describing your use case---it's totally fair. We will explore how we can improve insights as a whole and also how we can improve the Slack integration.\n\nSupporting insights in automation is also on our long-term roadmap. So, unfortunately, today, there is nothing additional you can do, but when we tackle one of these three topics, you should be able to see some improvements there.\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n"
},
{
"author": "Gilad Waldman",
"body": "Thank you, I assume there is no Jira ticket i can follow to track progress?\n"
},
{
"author": "Hermance NDounga",
"body": "No we aren't working with publicly available tickets, but you can subscribe to the group, we are posting regularly on things we are working on, there is also our public roadmap, and in general we are making in product announcement when we ship new functionalities.\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n"
}
]
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Polaris-Datapoint-Link-Triggered-automation/qaq-p/2771439 | null |
{
"author": "jimmy.koutsoukis",
"title": "Delivery status not displaying on linked delivery ticket",
"body": "I don't see a status displayed at all when linking an epic to an idea. I see the linked epic, but the status doesn't come over from my delivery board at all. Help\n"
} | [
{
"author": "Hermance NDounga",
"body": "Hello everyone\n\nThanks for raising the issue, the bug should now be fixed.\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n",
"comments": null
},
{
"author": "Erin Perkins",
"body": "I am seeing the same issue with Delivery Progress and Delivery Status being blank.\n\n![JIRA_Discovery_Delivery_Epics.png](https://community.atlassian.com/t5/image/serverpage/image-id/338973iFAF33EBE9916C774/image-size/large?v=v2&px=999 \"JIRA_Discovery_Delivery_Epics.png\")![JIRA_Discovery_Delivery_View.png](https://community.atlassian.com/t5/image/serverpage/image-id/338975i5F2FCD3B86E97A0A/image-size/large?v=v2&px=999 \"JIRA_Discovery_Delivery_View.png\")\n",
"comments": null
},
{
"author": "Nick H",
"body": "Hi [@jimmy.koutsoukis](/t5/user/viewprofilepage/user-id/5556839) ,\n\nCan you share any screenshots of what you are seeing? Personally I cannot reproduce it with some tests just now as shown below:\n\n![del1.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/338970iC4A70464F224320D/image-size/large?v=v2&px=999 \"del1.jpeg\")![del2.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/338969i0A2ECDB41D5DA4F5/image-size/large?v=v2&px=999 \"del2.jpeg\")\n",
"comments": [
{
"author": "Gary Spross",
"body": "[@Nick H](/t5/user/viewprofilepage/user-id/2540930) , we opened a support ticket about this issue earlier and are still awaiting a reply.\n\n<https://support.atlassian.com/requests/JST-1024295/>\n"
},
{
"author": "Nick H",
"body": "Thank you [@Gary Spross](/t5/user/viewprofilepage/user-id/5166286) and everyone for reporting this. We're currently investigating the issue and will be in touch soon.\n"
},
{
"author": "Gary Spross",
"body": "[@Nick H](/t5/user/viewprofilepage/user-id/2540930), the Delivery Progress \\& Delivery Status values are showing again for us. I haven't received an update on our support ticket though. Any idea what the issue was and how it was addressed?\n"
}
]
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Delivery-status-not-displaying-on-linked-delivery-ticket/qaq-p/2770842 | null |
{
"author": "Mark Lang",
"title": "JQL query for PD",
"body": "Hi,\n\nWe have numerous JD projects, and I am trying to use JQL queries for some reports. However, I'm encountering an issue where multiple custom fields with the same names appear, making it unclear which field belongs to the specific project I'm focusing on. For instance, when I query the test project, I get 15 different custom fields with the same name, each used for different PD projects. It's a complicated process to identify which field corresponds to which project. The same issue arises when I try to add columns in a JQL query, as all these fields show up with identical names. I was hoping that if at least a project is used, it would filter the custom fields based on that project.\n\n![2024-07-30_8-30-22.png](/t5/image/serverpage/image-id/338888iC654374DCDD7D5DE/image-size/large?v=v2&px=999 \"2024-07-30_8-30-22.png\")\n"
} | [
{
"author": "YY Brother",
"body": "Hi [@Mark Lang](/t5/user/viewprofilepage/user-id/5556450)\n\nWelcome to our Community.\n\nTo fix the issue of multiple same names, I think you could use the global custom fields instead, which can be shared among those JPD projects.\n\n![Xnip2024-07-31_00-50-31.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/338919iE3F9F767432CC2EA/image-size/large?v=v2&px=999 \"Xnip2024-07-31_00-50-31.jpg\")\n\nAs for JQL queries, please use this rest api to get the custom field id: \nhttps://{site name}.atlassian.net/rest/api/3/issue/{issue key}\n\n![Xnip2024-07-31_00-53-43.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/338921iFF2E99591ED4AAE2/image-size/large?v=v2&px=999 \"Xnip2024-07-31_00-53-43.jpg\")\n\nHope it helps you,\n\nYY?\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/JQL-query-for-PD/qaq-p/2770550 | null |
{
"author": "Kristen Ocelnik",
"title": "Published stakeholder view embedded in Confluence isn't visible to Confluence users",
"body": "I am trying to embed one of our Product Discovery views into Confluence via the 'copy URL' for our non-Jira users to see. The correct Confluence users group and 'everyone with the link has access' is marked \\& even individually added names; however, no one without Jira access can view the information - they receive a gray empty box in its place.\n\nI believe this was working fine yesterday when I had someone test it for me; is there an issue that may be causing this today? They are logged into Confluence, are part of the right groups, and the Discovery view is 'published'. They can't seem to view it from the URL or from the embedded macro.\n\nThank you!\n"
} | [
{
"author": "Hermance NDounga",
"body": "Hi Kristen,\n\nwe aren't able to reproduce - we tested with a confluence only user, added in the list of stakeholders, and display the published view on a confluence page, the confluence only user can both see the published view, as well as the published view in Confluence.\n\nif you still have the issue; can you please raise a support ticket using the \"give feedback\" button and select the support teams.\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Published-stakeholder-view-embedded-in-Confluence-isn-t-visible/qaq-p/2770544 | [
"cloud",
"jira-product-discovery"
]
|
{
"author": "Andre de Castro",
"title": "Delivery progress does not show progress",
"body": "When I attach a delivery ticket to an idea, the delivery status on the Jira Product Discovery board does not reflect the status of the linked ticket. The progress bar no longer appears. \nWhat could be wrong? \n\n<br />\n\n<br />\n\n![Progress.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/338931iB7932E1864A65E78/image-size/large?v=v2&px=999 \"Progress.JPG\") \n\nPreviously it was like this... \n\n![Progress 2.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/338934i2FC46AF3DBE472BE/image-size/large?v=v2&px=999 \"Progress 2.JPG\")\n"
} | [
{
"author": "Hermance NDounga",
"body": "Hello everyone, \nthank you for raising this issue, \nthe bug should now be fixed.\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n",
"comments": [
{
"author": "Andre de Castro",
"body": "Thank you.\n"
}
]
},
{
"author": "Josh White",
"body": "Same for me - Delivery Progress disappeared a few days ago \nThis issue affects both the Delivery tab on an Idea as per the above, but it also affects the delivery progress on the Roadmap view and the Timeline view\n",
"comments": [
{
"author": "Gary Spross",
"body": "Same for us (although we only noticed them missing as of yesterday). We had opened a support ticket with Atlassian, but still haven't received an answer. As of this morning, the values for those fields appear to be displaying again. I'm awaiting a response on our support ticket to find out what the problem was exactly.\n"
}
]
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Delivery-progress-does-not-show-progress/qaq-p/2770713 | null |
{
"author": "Michael.Fiterman",
"title": "Deleted ideas reappear after import",
"body": "Hi All!\n\nI'm new to JPD and I'm trying to import ideas from a CSV file. The import is working fine, but every time I import, some of the ideas I previously deleted from JPD are reappearing after the import.\n\nSo I get not only the newly imported ideas, but also the old ones, which were deleted and showed 0 ideas after deletion.\n\nI tested with importing a single idea only and the previously deleted 700 appeared back there after the import. The import log only the idea that I imported.\n\nAny thoughts?\n\nThanks!\n"
} | [
{
"author": "Hermance NDounga",
"body": "Hey Michael,\n\nCan you please open a ticket with our support teams?\n\nin Jira Product Discovery, at the bottom of the left panel click \"give feedback\" and then select support teams. this definitely sounds like a bug, we need to investigate in your instance.\n\nThanks in advance,\n\nBest Regards, \nHermance \nProduct Manager @ Jira Product Discovery\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Deleted-ideas-reappear-after-import/qaq-p/2770224 | null |
{
"author": "Yuliia Vyborova",
"title": "Freeze a view in JPD",
"body": "Hello! \nWe are working on roadmap and need to freeze view to export data from JPD to a document. Is there a way to lock a certain view from editing beyond lowering Role for users (making them read-only)?\n\nAlternatively, what Auto-saved toggle does? If I disable it - does it mean changes in fields won't be saved?\n"
} | [
{
"author": "Nick H",
"body": "Hi [@Yuliia Vyborova](/t5/user/viewprofilepage/user-id/3597151) ,\n\nThis article may help clarify the auto-save toggle / feature a bit more: [Use filters, advance sorting and autosave](https://support.atlassian.com/jira-product-discovery/docs/use-filters-sorting-and-autosave/)\n> **Autosave** - This feature enables you to lock and unlock the settings you've configured in a view. This feature is useful for teams that collaborate in the same view and want to play around with setting changes without affecting everyone's view. \n> When **Autosave isn't enabled**, the changes you made to a view previously are locked in, however, if you make new changes, they appear in color yellow and are temporary.\n>\n> * If you switch views, the changes in yellow are lost.\n>\n> * If you *save for everyone,*changes are applied and saved for good.\n>\n> * If you save the changes in a new view, the view you made the changes in remains unaltered.\n>\n> When **Autosave is enabled**, changes you make to a view are saved permanently and you can't revert to a previous selection.\n\nEven when this feature is disabled, any changes to a field's values will save. This feature only affects the View specifically, and essentially freezes what is configured in the View prior the the toggle being disabled.\n\nYou can also save the View when this toggle is disabled after changes are made to the View. But if the changes are not saved, the View will be reverted back to the previous configuration.\n\nHope that helps! Maybe play around with this feature to see if it'll meet your use case.\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Freeze-a-view-in-JPD/qaq-p/2769365 | null |
{
"author": "Brendan Byers",
"title": "JPD how to create a list view for all ideas within a specific date range?",
"body": "I'm trying to create a list view in Jira Product Discovery that filters ideas between two specific dates.\n\nI can easily do this with a timeline view: \n![JPD Date Range.png](/t5/image/serverpage/image-id/338699i7AB8D05BD2D497DC/image-size/large?v=v2&px=999 \"JPD Date Range.png\")\n\nBut I cannot figure out how to create a list view with the exact same criteria.\n\nThe other option I'm pondering would setting up an Automation to add a label reflecting the appropriate Fiscal Quarter depending on the Project Start and Target dates, and to use those label to create the views I need if there isn't an easier solution.\n"
} | [
{
"author": "Axel Sooriah",
"body": "Hi [@Brendan Byers](/t5/user/viewprofilepage/user-id/845582)\n\nthanks for your question.\n\nYou can achieve this by using a filter on Project Start date and Project Target date.\n\nPlease see screenshots below.\n\nDo let us know if this helps. :)\n\n![Screenshot 2024-07-30 at 09.38.39.png](https://community.atlassian.com/t5/image/serverpage/image-id/338758i5CA0C13D30F41CA2/image-size/large?v=v2&px=999 \"Screenshot 2024-07-30 at 09.38.39.png\")\n\n![Screenshot 2024-07-30 at 09.38.49.png](https://community.atlassian.com/t5/image/serverpage/image-id/338757iA2E63086E8D5EF2D/image-size/large?v=v2&px=999 \"Screenshot 2024-07-30 at 09.38.49.png\")\n",
"comments": [
{
"author": "Brendan Byers",
"body": "Not quite unfortunately. \n\nMy team wants to see all ideas being worked on between two specific fixed dates. \nSo they want a Q2 view that shows everything between April 1st and June 30th and ideally want to refer back to this view later on in the year.\n\nThe relative dates would require monthly maintenance to ensure the view remains accurate as far as I understand. \n\nI assume this is the only option currently available? \n\nThank you.\n"
}
]
}
]
| https://community.atlassian.com/t5/Jira-Product-Discovery-questions/JPD-how-to-create-a-list-view-for-all-ideas-within-a-specific/qaq-p/2769649 | [
"date-time",
"jpd-filters"
]
|
{
"author": "Jin Budelmann",
"title": "Getting 403 when creating opsgenie incident but incident is still created",
"body": "I am setting up a datadog workflow to create opsgenie incidents and I am using the Create Incident action. It fails with a 403 error but still actually creates the incident with all the correct information. I want to use the result of this in a subsequent step so need this to succeed. Is this a opsgenie bug or a config issue somewhere?\n"
} | [
{
"author": "Mubeen Mohammed",
"body": "Hello [@Jin Budelmann](/t5/user/viewprofilepage/user-id/5535223)\n\nThank you for contacting the Atlassian Community. This is Mubeen.\n\nThe issue you noticed with the 403 error may only be possible with Insufficient permissions. There are no known issues with Opsgenie incident creation that can result in these errors with no impact on incident creation.\n\nThis may be possible if you have a custom script that involves Incident creation and follow-up script options that result in 403 errors. It is recommended that you verify the API key you are using and make sure it has the required permissions(Try with a Global API integration key with all the permissions enabled).\n\nAfter the API key verification also, if you continue to experience the same behaviour, then please open a support ticket with us at <https://support.atlassian.com/contact/> explaining the Incident creation flow you are currently using so we can further validate this with your account details. \n\nI hope the details provided are helpful. \n\nRegards\n\nMubeen Mohammed\n\nCloud Support Engineer\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/Getting-403-when-creating-opsgenie-incident-but-incident-is/qaq-p/2743366 | null |
{
"author": "Graham Lea",
"title": "OpsGenie to Microsoft Teams - For Information Only",
"body": "Hi team\n\nI have configured an OpsGenie to Microsoft Teams V2 integration which is working fine. Because it's a bi-directional integration I get the necessary controls to manipulate the alert from the teams channel.\n\nI'd like to have a second channel which is configured '++**for information only**++' The idea being that the engineers can manipulate the alert from within teams via the first integration but a wider audience just see the notification without the option to change the alert status.\n\nIs this possible and if it is is there any guidance on the settings required?\n\nRegards\n\nGraham\n"
} | [
{
"author": "Mubeen Mohammed",
"body": "Hello [@Graham Lea](/t5/user/viewprofilepage/user-id/5254229)\n\nThank you for contacting the Atlassian community. This is Mubeen.\n\nThe direct, inbuilt functionality to send alert details in a read-only format without the interactive alert actions (such as acknowledge, close, etc.) through the standard OpsGenie to Microsoft Teams integration is not a feature available. The integration's primary value proposition is around actionable alerts to streamline the response process.\n\nA workaround option could be utilizing OpsGenie's ability to send alert notifications via email. You can setup a channel in MS Teams to receive email notifications and configure OpsGenie to send alerts to that email address. While this method does not use the direct OpsGenie to Teams integration, it achieves the goal of delivering alerts in a read-only format to a Teams channel. This would require validations from your MS teams admin for the ability to get emails for your MS Teams channels.\n\nThank you for your time and consideration. \n\nRegards\n\nMubeen Mohammed\n\nCloud Support Engineer\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/OpsGenie-to-Microsoft-Teams-For-Information-Only/qaq-p/2741839 | [
"cloud",
"opsgenie-cloud",
"read-only",
"teams"
]
|
{
"author": "rob prest",
"title": "Issue triggering action policy from received email integration.",
"body": "Hi, I am working on part of a workflow in which I need to parse an existing Opsgenie alert reference from an email (Email integration with a regex search) and then update this Alert with a reference pulled from the email. This part is working, however I also need to then trigger OEC via an action policy (this part doesn't look to be being triggered) so that further steps can be taken on the server. \n\nIs this being blocked because the email integration then blocks the action policy, or am I trying to do something which isn't possible? If so, is there a workflow that I should be using in this case? \n\nThe email integration has \"If message contains\" , and within \"Action Policies\" I have:\n\n\"Match if one or more conditions\" \n\"message contains\" and then the string that it is checking for on the email integration \nthen:\n\nExecute action: and the action which would then be picked up by OEC.\n\n<br />\n\nBut I am not seeing anything coming through to OEC or logs seen in the alert that this action has been done. \n\nThank you for any advice that you can provide, \nKind regards, \nRob\n"
} | [
{
"author": "John M",
"body": "[@rob prest](/t5/user/viewprofilepage/user-id/5533308) Also keep in mind that action policies are only applied if the team where the policies is configured is also the owner team of the alert.\n",
"comments": [
{
"author": "rob prest",
"body": "Thank you, yea it does look to be the same team. I will get a support ticket raised\n"
}
]
},
{
"author": "Chris DeGidio",
"body": "Hi Rob,\n\nThis sounds like a very particular/specific workflow and issue. We would request that you submit the details to the Opsgenie support team under support.atlassian.com\n\nOur team will then be able to gain access to the account to check full configurations and look at some example alerts that aren't quite working right.\n\nThanks so much!\n\n- Chris\n",
"comments": [
{
"author": "rob prest",
"body": "Thanks Chris, I will get a support ticket raised now, \n\nKind regards, \n\nRob\n"
}
]
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/Issue-triggering-action-policy-from-received-email-integration/qaq-p/2741071 | null |
{
"author": "Marc Emanuel",
"title": "how to filter upon failure of merging a pr into a specific branch in GitHub",
"body": "We only want an alert when a pr is merged into main in GitHub\n"
} | [
{
"author": "Egor",
"body": "Hey Marc, \nThanks for reaching out to Atlassian Community! \n\nTo filter and receive alerts only when a pull request is merged into the main branch in GitHub, you need to configure the GitHub integration in Opsgenie. Set up a condition in the integration settings to check if the target branch of the merged PR is main. This way, you'll only get alerts for PRs merged into the main branch. \n\nCondition for the Target Branch: \n\n{ \n\"condition\": \"equals\", \n\"key\": \"pull_request.base.ref\", \n\"value\": \"main\" \n} \n\nBest Regards, \nEgor\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/how-to-filter-upon-failure-of-merging-a-pr-into-a-specific/qaq-p/2739044 | [
"cloud"
]
|
{
"author": "Armitha Reddy Toorpu Ceema",
"title": "Standalone Opsgenie",
"body": "Hi Team,\n\nWe are using standalone Opsgenie, and we use tags to categorize the alerts. I have one concern: if alerts are coming regarding servers, there may be different servers. For example, one alert might be for a server lock and another for a 07f1server block. The alerts regarding servers should go under only one tag and should not create different tags for each server alert. Is it possible to achieve this? If yes, how can it be done?\n\nThanks \\& Regards,\n\nArmitha Reddy Toorpu Ceema,\n\nAtlassian Engineer.\n"
} | [
{
"author": "Egor",
"body": "Hey Armitha, \nThanks for reaching out to Atlassian Community! \n\nYes, it is possible to categorize all server-related alerts under a single tag in Opsgenie. You can achieve this by using regular expressions (regex) in your integration settings to ensure that different variations of server alerts are grouped under a common tag. Here's how:\n\n1. **Create a Regular Expression**:\n\n- Develop a regex pattern that matches different variations of server alerts. For instance, if your alerts include terms like \"server lock\" or \"07f1server block,\" you can use a pattern to capture these variations.\n\n2. **Update Integration Settings**:\n\n- Go to your Opsgenie integration settings where you define your alert rules.\n\n- Add a condition to check if the alert message matches your regex pattern for server-related alerts.\n\n- Apply a common tag, such as server-alert, to all alerts that match this pattern.\n\nBy using this approach, all server-related alerts will be tagged uniformly, helping you avoid the creation of multiple, slightly different tags for similar alerts. \n\nBest Regards, \nEgor\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/Standalone-Opsgenie/qaq-p/2738958 | [
"cloud",
"opsgenie-cloud"
]
|
{
"author": "Noelle Ressler",
"title": "Android phone does not ring when getting notification",
"body": "About 6 months or so ago my phone stopped ringing when I get an on-call notification. I only receive a text message. I would prefer it to ring. I have an Android phone. Nothing has changed other than the usual system updates from Android. I would like to get this fixed.\n\nThank you...\n"
} | [
{
"author": "Egor",
"body": "Hey Noelle, \nThanks for reaching out to Atlassian Community! \n\nBasically, there are a few steps you need to check: \n\n1. Go to your Opsgenie account \\>\\> Settings \\>\\> Notifications and check if your \"Schedule Start\" action is set properly. \n\n2. Check if your app has permission to send you notifications. \n\nThere are more troubleshooting steps can be found here - <https://support.atlassian.com/opsgenie-android/docs/troubleshooting-for-android/> \n\nI hope this helps! \n\nBest Regards, \nEgor \n",
"comments": null
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/Android-phone-does-not-ring-when-getting-notification/qaq-p/2736979 | [
"cloud",
"opsgenie-cloud"
]
|
{
"author": "Brett Himmelright",
"title": "Alert-export-result",
"body": "Is it possible to have the alert level (example P1 - P4) be added to the data that is downloaded within the final alert data .csv?\n\nCurrently have\n\nAlert ID, Alias, TinyID, Message, Status, IsSeen, Acknowledged, Snoozed, CreatedAt, CreatedAtDate, UpdatedAt, UpdatedAtDate, Count, Owner, Teams.\n\nIt would be super beneficial if the alert level was included.\n\nThank you,\n\nBrett Himmelright \n"
} | [
{
"author": "Egor",
"body": "Hey Brett, \nThanks for reaching out to Atlassian Community! \n\nThis is true, when exporting alerts via UI, there's no priority field included. \n\nWorkarounds: \n\n1. You can get the list of alerts using our API -\n\nExample API call: GET <https://api.opsgenie.com/v2/alerts> \n\n2. You can get the list of alerts with priority field under the Analytics tab. \nYou need to go to your Opsgenie account \\>\\> Analytics \\>\\> Alert Analytics \\>\\> Scroll down to Alert Details View and then you'll see the list of all alerts with priority in it. \n\nYou can also download this report using CSV on the top right. \n\nPlease let me know if it helps.\n\nBest Regards, \nEgor\n",
"comments": [
{
"author": "Brett Himmelright",
"body": "Thank you, this worked for me, I appreciate this [@Egor](/t5/user/viewprofilepage/user-id/3583730)\n"
}
]
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/Alert-export-result/qaq-p/2735190 | null |
{
"author": "Allana Daudt",
"title": "Alerts Not Closing Properly in New Relic When Closed via Slack Button",
"body": "I am experiencing an issue with the integration between New Relic, Opsgenie and Slack, where alerts are not being closed as expected. Here are the details of the problem: \n\n* I have configured alerts in New Relic using OpenTelemetry.\n* When an alert is triggered in New Relic, it sends a notification to an Opsgenie webhook.\n* Opsgenie, in turn, sends a notification to a Slack channel.\n* When I close an incident via the Slack notification, it correctly closes the incident in Opsgenie.\n* However, the incident remains open in New Relic for the defined time period, which is 1 hour.\n* After this 1-hour period, when New Relic closes the incident, Opsgenie sends the same incident notification again for Slack channel, even though there is no ongoing issue. \n\nWhat could be causing this behavior and how to resolve it?\n"
} | [
{
"author": "Brennan Kiely",
"body": "Hi [@Allana Daudt](/t5/user/viewprofilepage/user-id/5527669) ,\n\nThanks for reaching out! I would suggest creating a support ticket at support.atlassian.com for this so we can get a look at your setup. There isn't a known issue with this flow, so it's tough to say what could be causing it without looking at an example.\n\nThanks!\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/Alerts-Not-Closing-Properly-in-New-Relic-When-Closed-via-Slack/qaq-p/2734783 | null |
{
"author": "Ji?? Wetter",
"title": "Azure integration doesn't offer tags field",
"body": "Hi,\n\nI have set up tags for certain alerts in the Azure portal. Unfortunately Azure integration does not offer such Dynamic properties. I also looked in payload and I don't see it there either. Maybe I'm looking the wrong way. Have you solved this?\n"
} | [
{
"author": "Egor",
"body": "Hey Ji??, \nThanks for reaching out to Atlassian Community! \n\nUnfortunately, the Azure integration with Opsgenie does not currently support dynamic properties such as tags. It appears these tags are not included when alerts are sent from Azure to Opsgenie. This means that tags set in the Azure portal do not carry over to Opsgenie alerts.\n\nAs of now, there is no built-in functionality to include these tags directly in the alert payload. We recommend monitoring the Opsgenie and Azure integration updates for any future enhancements regarding this feature.\n\n<br />\n\nBest Regards, \nEgor\n",
"comments": [
{
"author": "Ji?? Wetter",
"body": "Thanks for explanation.\n"
},
{
"author": "Ji?? Wetter",
"body": "[@Egor](/t5/user/viewprofilepage/user-id/3583730), is there any feature request (ticket) or something similar what can be watched?\n"
}
]
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/Azure-integration-doesn-t-offer-tags-field/qaq-p/2733366 | null |
{
"author": "Duy Le",
"title": "Delay integration trigger",
"body": "Is there any way to delay the integration trigger in Opsgenie?\n\nWe use Zendesk integration to create a Zendesk ticket whenever an Opsgenie Alert is created. The problem is most of the alerts would be auto-closed after a while, and we don't want ZD tickets for those alerts. Is there any way to delay this integration trigger, so that if the alert is auto-closed in the delay duration we don't create a ZD ticket for it?\n"
} | [
{
"author": "Tejaswi G",
"body": "Hi Duy Le,\n\nThis is Tejaswi from the Opsgenie Team, and I am happy to help.\n\nWe don't have a direct delay Option in Opsgenie to delay the triggering of the integration. The integration will be triggered as soon as the alert is assigned to a team.\n\nHowever, you can create a separate Team, *\"Team ZD,\"* which will have only the Zendesk integration in it, and add this team as a responder in the escalation rule after your required delay in the Original Team's escalation, where the alert is created to induce the delay for ZD ticket creation.\n\nKind Regards,\n\nTejaswi\n",
"comments": [
{
"author": "Duy Le",
"body": "That's brilliant. Thank you for your support, I'll test it and get back\n"
},
{
"author": "Duy Le",
"body": "![Screenshot 2024-06-25 165146.png](https://community.atlassian.com/t5/image/serverpage/image-id/331597i9D20A618F5F391B2/image-size/large?v=v2&px=999 \"Screenshot 2024-06-25 165146.png\")\n\nI've tried as you recommended, the delay is working, but the Zendesk integration wasn't triggered after the delay.\n\n<https://support.atlassian.com/opsgenie/docs/outgoing-integration-triggers-for-team-routings/>\n\nAccording to this article, the integration trigger should be working. Don't really know where I'm wrong though\n"
},
{
"author": "Tejaswi G",
"body": "Hi Duy Le,\n\nThank you for the update. Can you please log a ticket with us at <https://support.atlassian.com>? we would like to review your current team setup.\n\nKind Regards, \nTejaswi\n"
},
{
"author": "Duy Le",
"body": "Sure, thank you Tejaswi\n"
}
]
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/Delay-integration-trigger/qaq-p/2732936 | [
"cloud",
"opsgenie-cloud"
]
|
{
"author": "Andrew Shewchenko",
"title": "How do we disable the phone-answering service on an integrated phone number?",
"body": "Our team does not want to receive interactive phone calls through OpsGenie (the functionality is really bad, slow to connect, difficult to hear, leaves everyone frustrated, and often results in the whole team being escalated to due to the slowness in OpsGenie connecting the call), but we still want to be able to receive SMS messages to said number.\n\nIs there a way to disable this functionality while retaining the SMS? If not possible, is there a way to automatically route interactive phone calls to an answering service that will transcribe to text and send that in an alert to the escalation group receiving it?\n\nWe're at a loss with this, as the feature as currently implemented is very frustrating for us, and ultimately leading us to look at other options for our oncall.\n"
} | [
{
"author": "Andrew Shewchenko",
"body": "[Documentation on call routing](https://support.atlassian.com/opsgenie/docs/incoming-call-routing/)\n\nBuried at the bottom of the page: \n\nIf you want to use call routing only for taking voicemails, and notify your on-call team member but not actually dial them, you can set \"How many users should be tried\" to zero in the configuration, under \"Other Settings\" section and save the integration.\n",
"comments": null
},
{
"author": "Nicolas Grossi",
"body": "[@Andrew Shewchenko](/t5/user/viewprofilepage/user-id/5525613) Welcome, what is your license type ? If you have an active license you might contact support.atlassian.com.\n\nI guess that feature is not available currently.\n\nNicolas\n",
"comments": [
{
"author": "Andrew Shewchenko",
"body": "We're on Standard. it looks like Atlassian's preference is for questions/issues like this to hash out in public first and tickets later, so I started here - but I'll see what Support says.\n"
}
]
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/How-do-we-disable-the-phone-answering-service-on-an-integrated/qaq-p/2732769 | [
"phone"
]
|
{
"author": "Surajit Paul",
"title": "How to route alerts through various channels based on priority",
"body": "Hi,\n\nBy default all alerts are sent to a slack channel from OpsGenie irrespective of the priority of the alert. How can we setup multiple channels e.g. slack/email etc. and route the alert to a channel based on the priority?\n\nThanks.\n"
} | [
{
"author": "Nicolas Grossi",
"body": "[@Surajit Paul](/t5/user/viewprofilepage/user-id/5012373) welcome! You might take a look at this thread: <https://community.atlassian.com/t5/Opsgenie-questions/Change-priority-dinamically-based-on-the-number-of-consecutives/qaq-p/1870572>\n\nNicolas\n",
"comments": null
},
{
"author": "Surajit Paul",
"body": "Thanks [@Nicolas Grossi](/t5/user/viewprofilepage/user-id/676185) we are looking for a flexible routing solution based on the priority of an alert e.g. P1 and P4 should be routed to 2 different channels, we are not looking for a routing solution based on frequency or count of a frequent alert. Is there a way to support multiple channels from a team setup?\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/How-to-route-alerts-through-various-channels-based-on-priority/qaq-p/2732760 | [
"cloud",
"opsgenie-cloud"
]
|
{
"author": "tonywu",
"title": "Opsgenie, unable to login from Opera browser",
"body": "Hi,\n\nWondering if anyone has problem logging into Opsgenie from Opera browser. My observations:\n\n1. It works from incognito mode, which would imply it may be some sort of cookie or cache issue. Tried clearing cache on the entire browser twice, and got it to work for maybe a day, then started to fail again.\n\n2. No problem with Chrome.\n\nThis is probably one of those gray areas sort of thing. But would love to know if someone else has run into this, and if there is perhaps a workaround.\n"
} | [
{
"author": "Nicolas Grossi",
"body": "[@tonywu](/t5/user/viewprofilepage/user-id/4860501) Opera is not supported: <https://support.atlassian.com/opsgenie/docs/supported-web-browsers/>\n\nNicolas\n",
"comments": [
{
"author": "tonywu",
"body": "Thanks, that is good to know. A feature request it is.\n"
}
]
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/Opsgenie-unable-to-login-from-Opera-browser/qaq-p/2732331 | [
"cloud",
"opsgenie-cloud"
]
|
{
"author": "Ergo Sims",
"title": "Alert not closed notification",
"body": "Hey.\n\nWe have a rule to notify response team if alert is not closed in time. Although there are many different notification flows available (note added, schedule start-end etc.) there doesn't seem to be possibility to have separate notification rule for \"alert not closed\". Is there a way to have separate rule for that (don't want a call, just push notification or email is enough)?\n\nThanks in advance.\n"
} | [
{
"author": "Tejaswi G",
"body": "Hi [@Ergo Sims](/t5/user/viewprofilepage/user-id/5524177)\n\nThis is Tejaswi from the Opsgenie team and here to help.\n\nWe don't have a separate notification rule(flows) for the existing alerts and you will be notified via a new alert rule if you are added as a responder via the escalation rules or if you are notified again via it.\n\nIf you have any further queries, Please log a ticket with us at <https://support.atlassian.com/contact>\n\nKind Regards,\n\nTejaswi\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/Alert-not-closed-notification/qaq-p/2730859 | null |
{
"author": "Jason Rogers",
"title": "How to add Jira Integration in OpsGenie?",
"body": "Hi guys,\n\nI feel like this should be an easy ask, but we are using Jira SM and JSW Cloud and I have set up a Service project and also an OpsGenie rota, based on our Operations Team. \n\nI have gone to Integrations to add in Jira, but it is not listed as an option anymore. I know it used to be and according to this documentation, it still is...\n\n![Atlassian image4.PNG](/t5/image/serverpage/image-id/330628iB26A7B8D66FB4912/image-size/large?v=v2&px=999 \"Atlassian image4.PNG\")\n\n<https://confluence.atlassian.com/jirakb/create-an-opsgenie-alert-after-jira-issue-priority-is-updated-1142438970.html>\n\nAll I want to is create an alert for when an high priority issue is created. I can not find anything in the automations that can assist either (Like a create Alert action).\n\nAny help would be appreciated.\n\nCheers,\n\nJ\n"
} | [
{
"author": "Jason Rogers",
"body": "So the answer is that now you can add JSW or JSM integrations via Syncs. This is a new feature in JSM/OpsGenie Cloud sites (although only some sites will have this).\n\nMore info on Syncs here: <https://support.atlassian.com/jira-service-management-cloud/docs/sync-alerts-with-service-and-software-projects/>\n\nThanks for all your help!\n",
"comments": null
},
{
"author": "Jason Rogers",
"body": "FYI, I am also following this <https://support.atlassian.com/opsgenie/docs/integrate-opsgenie-with-jira-service-management-cloud/> and it says I need to add the integration via Integrations, but there is no Jira Cloud integration available (see screen shot above)\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/How-to-add-Jira-Integration-in-OpsGenie/qaq-p/2731109 | [
"jira"
]
|
{
"author": "Narendiran Rengamani",
"title": "opsgenie schedule override option not showing for user",
"body": "all my team mates have roles as USER. they do not see the option of OVERRIDE on their shift schedule, but being admin i can see that option.\n\nas explained in article - <https://support.atlassian.com/opsgenie/docs/override-an-on-call-schedule/> \n\nOverride an on-call schedule {#toc-hId--355065654}\n--------------------------------------------------\n\nwe are trying to utilise this feature but dont see the option. any permission missing? please guide\n"
} | [
{
"author": "Rafael Meira",
"body": "Hey [@Narendiran Rengamani](/t5/user/viewprofilepage/user-id/5522513) \n\nThis is normal behavior, as the user would have less access than other users or custom roles. \n\nYou can read more about it here: \n\n[https://support.atlassian.com/opsgenie/docs/learn-user-roles-and-permissions/#:\\~:text=Management%20is%20available).-,Creating%20New%20Custom%20User%20Roles,-When%20you%20switch](https://support.atlassian.com/opsgenie/docs/learn-user-roles-and-permissions/#:~:text=Management%20is%20available).-,Creating%20New%20Custom%20User%20Roles,-When%20you%20switch) \n\n<br />\n\nLet me know if you have any further questions. \n\n<br />\n\nBest, \nRafa\n",
"comments": [
{
"author": "Narendiran Rengamani",
"body": "Thank you\n"
}
]
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/opsgenie-schedule-override-option-not-showing-for-user/qaq-p/2729787 | [
"cloud",
"opsgenie-cloud"
]
|
{
"author": "Abhi Tanwar",
"title": "How to repeat individual escalation rule?",
"body": "Our requirements is like this - \n\nif A,B,C,D,E are in rotation schedule, if A doesn't ack alert after notifying 4 times (1 each minute), then we can notify to B, if B doesn't ack after being notified 4 times (1 each minute), then notify C, if C doesn't ack alert after being notified 4 times then inform D and so on. \n\nWill I have to set this up manually for each case or is there a way to setup looping rules or something?\n"
} | [
{
"author": "Tejaswi G",
"body": "Hi [@Abhi Tanwar](/t5/user/viewprofilepage/user-id/5523298),\n\nThis is Tejaswi from the Opsgenie Team, and I am happy to help.\n\nI understand you wish to notify each user four times before notifying the other on-call users in the rotation. We don't have a feature native to Opsgenie to achieve this use case. You can manually create an escalation rule with a 5-minute delay for each user, and then, in the user's profile, you can ask the users to repeat the notification in the notification rules in their profile.\n\nIf you don't want to have your engineers setup the notification profile to repeat, then the only option would be to set each user manually in the escalation rule 5 times each with 1 minute difference\n\nIf you have any further queries, Please log a ticket with us at <https://support.atlassian.com/contact>.\n\nKind Regards,\n\nTejaswi\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/How-to-repeat-individual-escalation-rule/qaq-p/2729721 | [
"cloud",
"opsgenie-cloud"
]
|
{
"author": "Lior Marantenboim",
"title": "On-Call hours report with new UI errors",
"body": "Dear all,\n\nSince the new UI on the Analytics part was deployed we have faced the issue of losing our previous scheduled report. We are not in the midst of closing the payroll for this month and don't have a proper working report from OpsGenie. I have tried creating an ad-hoc report from the dashboard but the calculations are completely wrong. I have also tried creating a new subscription with the new method, it sent me the report with errors and now it has disappeared.\n\nI have opened a support case within the tool and have been waiting for days for the engineering team to take a look.\n\nIs there any way to go back to the old UI temporarly until you fix all these issues? Having the report tool not work correctly affects people's payslip and creates a lot of overhead for the payroll team.\n\nBest regards\n\nLior.\n"
} | [
{
"author": "Mubeen Mohammed",
"body": "Hello [@Lior Marantenboim](/t5/user/viewprofilepage/user-id/5070972)\n\nThank you for contacting the Atlassian Community. This is Mubeen.\n\nWe truly appreciate your engagement and patience as we work through the challenges you're facing with the new Opsgenie analytics.\n\nWe understand how changes in tools and features can impact your workflow and the overall user experience. I would like to assure you that new analytics is aimed at providing enhanced functionality and a more robust analytics experience. As such, we are unable to revert to the old analytics system.\n\nWe are also mindful of the issues you've encountered with the new analytics, and I want to reassure you that your concerns are being addressed accordingly. Your ticket is currently open with our team, and we are diligently working on resolving the problems you've noticed as soon as possible. \n\nWe value your feedback as it is crucial for us to continue improving. If you have any further suggestions or concerns or need assistance with specific features of the new analytics, please don't hesitate to reach out directly on the open ticket. Our support team is here to help guide you through the transition and make this as smooth as possible for you. \n\nThank you for your understanding.\n\nRegards\n\nMubeen Mohammed\n\nCloud Support Engineer\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/On-Call-hours-report-with-new-UI-errors/qaq-p/2729525 | [
"cloud",
"opsgenie-cloud"
]
|
{
"author": "Narendiran Rengamani",
"title": "opsgenie schedule override option not showing for user",
"body": "all my team mates have roles as USER. they do not see the option of OVERRIDE on their shift schedule, but being admin i can see that option.\n\nas explained in article - <https://support.atlassian.com/opsgenie/docs/override-an-on-call-schedule/> \n\nOverride an on-call schedule {#toc-hId--355096536}\n--------------------------------------------------\n\nwe are trying to utilise this feature but dont see the option. any permission missing? please guide\n"
} | [
{
"author": "John M",
"body": "Hi [@Narendiran Rengamani](/t5/user/viewprofilepage/user-id/5522513) ,\n\nJohn from Opsgenie support, happy to assist here.\n\nUsers can add overrides for themselves only, whereas admins can add overrides for other users:\n\n<https://support.atlassian.com/opsgenie/docs/override-an-on-call-schedule/#Override-a-schedule>\n\nThis is a screenshot from a logged in user:\n\n![2024-06-18_14-04-08.png](https://community.atlassian.com/t5/image/serverpage/image-id/330476iF8BAD80BA5479EBC/image-size/large?v=v2&px=999 \"2024-06-18_14-04-08.png\")\n",
"comments": [
{
"author": "Narendiran Rengamani",
"body": "Thanks John\n"
}
]
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/opsgenie-schedule-override-option-not-showing-for-user/qaq-p/2728641 | [
"cloud",
"opsgenie-cloud"
]
|
{
"author": "Baron E. Schaaf",
"title": "Testing workflow from New Relic not generating alert in OpsGenie",
"body": "Used t[his page](https://support.atlassian.com/opsgenie/docs/integrate-opsgenie-with-new-relic-alerts-new/) as a guide to set up new relic integration with Opsgenie through a webhook.\n\nSet up integration on \"Freds On Call\" team page. Copied URL.\n\nSet up workflow destination in New Relic using copied URL.\n\nUsed the payload template defined here: <https://support.atlassian.com/opsgenie/docs/integrate-opsgenie-with-new-relic-alerts-new/>\n\nChanged team name to \"Freds On Call\". Changed tags and recipients to empty strings.\n\nWhen I click on \"Send Test Notification\", nothing appears in OpsGenie.\n\nWhat should I check or do next?\n"
} | [
{
"author": "?? ??(Sasou Mitsuhiro) lixiluser",
"body": "\"current_state\": {{#if issueClosedAtUtc}} \"closed\"\n\n?\n\n\"current_state\": {{#if issueClosedAtUtc}} \"open\"\n",
"comments": null
},
{
"author": "Nicolas Grossi",
"body": "[@Baron E. Schaaf](/t5/user/viewprofilepage/user-id/5316771) Are you sure that the URL is the correct one for your instances ?\n\nNicolas\n",
"comments": [
{
"author": "Baron E. Schaaf",
"body": "Replied to other answer.\n"
}
]
},
{
"author": "Nicolas Grossi",
"body": "[@Baron E. Schaaf](/t5/user/viewprofilepage/user-id/5316771) what is your OpsGenie license type ?\n\nNicolas\n",
"comments": [
{
"author": "Baron E. Schaaf",
"body": "Hey Nicholas,\n\nSubscription type is:\n\n* Essentials Trial (monthly)\n\nI copied the URL from the Opsgenie -\\> Teams-\\> My team-\\> Integrations -\\> New relic integration -\\> integration settings - steps\n\nand pasted it into New Relic -\\> Alerts -\\> Destinations -\\> Webhook -\\> destination.\n\nI also copied both and compared them in Beyond Compare.\n\n**New Relic Destination:**\n\nWebhook name -\\>OpsGenie\n\nEnpoint Url -\\> <https://api.opsgenie.com/gb/v1/json/integrations/webhooks/newrelicv2?apiKey={redacted>}\n\nAuthorization -\\> No authorization\n"
}
]
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/Testing-workflow-from-New-Relic-not-generating-alert-in-OpsGenie/qaq-p/2727593 | [
"new-relic"
]
|
{
"author": "Aaron Boyd",
"title": "HTTP failed: Request body is not processable. Please check the errors.",
"body": "Greetings folks,\n\nWe have a Microsoft Power Automate flow setup to monitor an alerting mailbox we have that receives alerts from various security tools that we use. This flow will extract the subject of the e-mail (using the subject trigger), and the body of the mail (using the body trigger) and take the outputs composing a message (subject output) with the description being the body of the e-mail to the Alerts API for OpsGenie.\n\nWe randomly started getting HTTP 422 status code errors (after making no changes to the flow) suggesting the message cannot be empty, when we can confirm the message is not empty within the body of the API POST request being made.\n"
} | [
{
"author": "Elelta D",
"body": "Hello Aaron,\n\nI see you are creating an alert by sending something like the message below to the alerts endpoint, but that it has suddenly stopped working after working fine and you see 422 errors event though you made no changes, is that the case?\n\ncurl -X POST <https://api.opsgenie.com/v2/alerts>\n\n-H \"Content-Type: application/json\"\n\n-H \"Authorization: GenieKey xxxxxxx\" -d\n\n'{ \"message\": \"An example alert message\"}'\n\nSometimes 422 Unprocessable Content response status code means that the content sent to Opsgenie could not be used, for example if you send the ID for an Opsgenie instance rather than the id of an MS tam channel in an Ms Team integration. The content is in the expected format and syntax but the ID is not correct.\n\nIf you would like to directly talk to someone in support about this issue I recommend that you open a ticket at <https://support.atlassian.com/contact/>\n\nBest\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/HTTP-failed-Request-body-is-not-processable-Please-check-the/qaq-p/2727458 | null |
{
"author": "Tony Rogers",
"title": "extract tags from an email integration",
"body": "Hi,\n\nIm working with an email integration in OG, im trying to find an easy way to pull field data from the message body in to tags?\n"
} | [
{
"author": "Nicolas Grossi",
"body": "[@Tony Rogers](/t5/user/viewprofilepage/user-id/5513628) Welcome!. The following doc has all the information regarding current integration: <https://support.atlassian.com/opsgenie/docs/integrate-your-email-with-opsgenie/>\n\nHTH\n\nNicolas\n",
"comments": [
{
"author": "Tony Rogers",
"body": "Thanks [@Nicolas Grossi](/t5/user/viewprofilepage/user-id/676185) I have read the guide, howevere, it is very basic and i am looking for the advanced functionality to pull data from the email body into tags (if possible, i believe it is)\n"
}
]
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/extract-tags-from-an-email-integration/qaq-p/2727348 | null |
{
"author": "Venz",
"title": "Details (Key-value based) condition Policy",
"body": "Hi Everyone!\n\nMy current setup is OpsGenie, JSM (Cloud), and Azure alerts. The integration is working as expected and we've been using it for some time now.\n\nI want to create a Team Policy in Opsgenie wherein it will filter out payload information of incoming Alerts from Azure Alerts. On the Azure side, there is key-value pair ***Custom properties**,* under an alert rule, that I can add to an alert as payload info.\n\n![CustomProperties.png](https://community.atlassian.com/t5/image/serverpage/image-id/329914i8ACA25FD8419CB22/image-dimensions/304x221?v=v2 \"CustomProperties.png\")\n\nNow in Opsgenie, I am wondering if I can use the condition ***Details (key-value based)*** to filter the ***Custom properties***from an Azure alert.\n\n![Key-value.png](https://community.atlassian.com/t5/image/serverpage/image-id/329915i728F088FC6EE1FE6/image-dimensions/335x216?v=v2 \"Key-value.png\")\n\nDoes anyone been using this? I know there are several posts regarding the Details (key-value based) but it doesn't point to want I need.\n\n\\**Pardon me with the blocked pictures. These are just an examples*\n"
} | [
{
"author": "Tejaswi G",
"body": "Hi [@Venz](/t5/user/viewprofilepage/user-id/5265420),\n\nThis is Tejaswi from the Opsgenie Team, and I am happy to help.\n\nYes, you can use these details in the Opsgenie filter condition as a key-value pair.\n\nIf you are facing any issues with these, Please feel free to reach out to us at <https://support.atlassian.com/contact>\n\nKind Regards,\n\nTejaswi\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/Details-Key-value-based-condition-Policy/qaq-p/2727288 | [
"cloud",
"jira-cloud"
]
|
{
"author": "Rai,Gursharan",
"title": "difference between opsgenie cozy and comfort views",
"body": "I am looking for difference between cozy and comfort views on OpsGenie. What's the advantage of using cozy vs comfort view for monitoring.\n"
} | [
{
"author": "Chris DeGidio",
"body": "[@Rai,Gursharan](/t5/user/viewprofilepage/user-id/5489537) Comfort view pulls the rows together a little closer. It's all personal preference :)\n\nHope this helps\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Opsgenie-questions/difference-between-opsgenie-cozy-and-comfort-views/qaq-p/2726182 | [
"cloud",
"opsgenie-cloud"
]
|
{
"author": "Bill Parlock",
"title": "Deleting a Bamboo repository link",
"body": "Does deleting a Bamboo repository link also delete the associated Bitbucket repository?\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello Bill,\n\nWelcome to atlassian community\n\nNo deleting a Bamboo repository will not delete the associated Bitbucket repository, hope this answers your query.\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": [
{
"author": "Bill Parlock",
"body": "Thank you. Apparently the Bamboo link to the Bitbucket repository is removed, but does not affect the Bitbucket repository.\n"
}
]
}
]
| https://community.atlassian.com/t5/Bamboo-questions/Deleting-a-Bamboo-repository-link/qaq-p/2649657 | [
"server"
]
|
{
"author": "Madhu",
"title": "How to get Meta data from bamboo plan",
"body": "Hi Team,\n\nI have two projects like,\n\nProject A Project B\n\nPlan A Plan B\n\nSo here i need to get Plan B variables to Plan A. can you please help me to get end point for this.\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello Madhu,\n\nWelcome to Atlassian community\n\nPlan B variables cab't be accessed to Plan A as they are part of different projects, As per your requirement you should be using Global variables.\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": [
{
"author": "Madhu",
"body": "Hi Shashank,\n\nIf i need to use global variables, can i configure with out admin access to the bamboo.\n\nif yes, can you please guide me the steps.\n"
},
{
"author": "Shashank Kumar",
"body": "Hi Madhu,\n\nNo you cannot, you'll need to have a minimum \"Restricted Admin\" access to create Global variables.\n\nRegards,\n\nShashank kumar\n"
}
]
}
]
| https://community.atlassian.com/t5/Bamboo-questions/How-to-get-Meta-data-from-bamboo-plan/qaq-p/2647744 | null |
{
"author": "Philipp Minkus",
"title": "Internal server error",
"body": "Hello,\n\nI installed the Server Version of Bamboo 6.8.1 with Eclipse Adoptium\\\\jdk-21.0.2.13-hotspot. When I follow the Setup Wizard, after entering the license I get\n\n```\nMethod \"execute\" failed for object com.atlassian.bamboo.ww2.actions.setup.SetupGeneralConfiguration@36ab6c3f [java.lang.ExceptionInInitializerError]\n```\n\n```\nCaused by: java.lang.ExceptionInInitializerError\n```\n\nIt would be very nice if you could help me.\n\nBest Regards,\n\nPhilipp Minkus\n"
} | [
{
"author": "Anik Sengupta",
"body": "Hello Phillip,\n\nWelcome to Atlassian community.\n\nIt's can be an issue related to Java version, please use 1.8u250 and below, versions 1.8u254+ cause overflow at H2 DB, see <https://jira.atlassian.com/browse/BAM-21018>\n\nAnother solution is to use non embedded DB like PostgreSQL or use Bamboo 7.1.1+\n\nPlease check the requirements for Bamboo 6.8 <https://confluence.atlassian.com/bamboo0608/supported-platforms-970618658.html>\n\nRegards,\n\nAnik Sengupta\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Bamboo-questions/Internal-server-error/qaq-p/2646527 | null |
{
"author": "Madhu",
"title": "How to check out code from one source code check with multiple branches",
"body": "Hi Team,\n\nI have requirement like one source code check out with multiple branches. is there any way to do it.\n\nThanks in advance!!\n\nRegards,\n\nMadhu Balineni\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello Madhu,\n\nWelcome to Atlassian community.\n\nWhen you save a linked repository in Bamboo you save it pointing to a particular branch.\n\nIf I understand correctly your questions is about if you can checkout multiple branches of a repository in **source code checkout task**. You can do this with some the below steps.\n\n1. Save all the branches which you want to checkout as a separate linked repository or plan repository or project repositories.\n\n2. In the source code checkout below, add all the repositories which you want to checkout, use the **Add repository** button\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/313357iA4CF0030DD30E02B/image-size/large?v=v2&px=999 \"image.png\") \nRegards,\n\nShashank kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Bamboo-questions/How-to-check-out-code-from-one-source-code-check-with-multiple/qaq-p/2645858 | null |
{
"author": "bhartendu kumar",
"title": "Unable to queue new build",
"body": "I am trying to queue a new build using API call\n\n### /queue/{projectKey}-{buildKey} {#toc-hId-2115990204}\n\nIf the concurrency is set to 1, API call is failing and unable to queue the build.\n\nI want the build to be in queue even if concurrency is set to 1, Let the InProgress build finish and wait in the queue\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello Bhartendu,\n\nWelcome to Atlassian community.\n\nIf you set concurrency to 1, it means at a given time only 1 build can run ( or even get into queue ), basically more than 1 builds can't be trigerred.\n\nIf you want to get the build into queue or run parallel you need to increase the concurrency.\n\nYou may have a requirement where you don't want build to run in parallel but builds to get queued, in this case you can increase the concurrency and dedicate a agent only for this build plan, in this way build will get queued.\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": null
},
{
"author": "bhartendu kumar",
"body": "Any suggestions?\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Bamboo-questions/Unable-to-queue-new-build/qaq-p/2643828 | null |
{
"author": "Rajkumar",
"title": "I didn't connect H2 database type",
"body": "I didn't connect H2 database type\n\n![bamboo date base.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/313099i00FD84779F5D7928/image-size/large?v=v2&px=999 \"bamboo date base.JPG\")![bamboo.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/313100i3BF587139878F8DD/image-size/large?v=v2&px=999 \"bamboo.JPG\")![jar file h2.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/313101i42D92ADB1F295A72/image-size/large?v=v2&px=999 \"jar file h2.JPG\")\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello Raj,\n\nIf i understand your problem correctly you put the jar for H2 DB in the bin directory and still Bamboo is not able to connect to it.\n\nCan you make sure you provide read/write access to this jar to the user which is running Bamboo service.\n\nStop and restart the Bamboo service and possibly delete bamboo.cfg.xml file before starting the service if this is new installation.\n\nLet me know if this works.\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": [
{
"author": "Rajkumar",
"body": "Thanks Shashank. it works\n"
}
]
},
{
"author": "Nic Brough -Adaptavist-",
"body": "Welcome to the Atlassian Community!\n\nI am sorry to say that that is not true. Atlassian applications use whatever database you select in the earlier screens. To get this error, you must have selected the H2 embedded database option.\n",
"comments": [
{
"author": "Rajkumar",
"body": "Thanks Nic\n"
}
]
}
]
| https://community.atlassian.com/t5/Bamboo-questions/I-didn-t-connect-H2-database-type/qaq-p/2645296 | null |
{
"author": "Snehal Jadhav",
"title": "how to pass values from \"Bamboo global\" to \"Deployment plan script\" which is running on windows",
"body": "wanted to pass values from \"Bamboo global\" to \"Deployment plan script\" which is running on windows agent\n"
} | [
{
"author": "Anik Sengupta",
"body": "Hi Snehal,\n\nThanks for contacting Atlassian community .\n\nYou can set up a Global variable as\n\n1. From the top navigation bar select  \\>**Build resources** \\> **Global variables**.\n2. Add, update, or delete the global variables, as desired:\n * **Add** a new variable once you have entered the key and value for it.\n\nGlobal variables can be accessed by using `${bamboo.globalVarName`}.\n\n![Screenshot 2024-03-18 at 10.56.19 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/312783i13C8EC6D9D855DCC/image-size/large?v=v2&px=999 \"Screenshot 2024-03-18 at 10.56.19 PM.png\")![Screenshot 2024-03-18 at 10.56.40 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/312784i2C0159D85934B1A7/image-size/large?v=v2&px=999 \"Screenshot 2024-03-18 at 10.56.40 PM.png\")![Screenshot 2024-03-18 at 10.56.57 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/312785iAA1B5BA14D6D06B3/image-size/large?v=v2&px=999 \"Screenshot 2024-03-18 at 10.56.57 PM.png\")\n\nRegards,\n\n**Anik Sengupta**\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Bamboo-questions/how-to-pass-values-from-quot-Bamboo-global-quot-to-quot/qaq-p/2643554 | null |
{
"author": "M Rizky Barokah",
"title": "Send File to my Remote Server IP",
"body": "Hello,\n\nI am new to Bamboo and Bitbucket, and new to programming world. I have already created my code in Bitbucket and linked it to my Bamboo project in the linked repository section. I would like to run this code using a script task in Bamboo, but I am unsure about the linked repository path in Bamboo. How can I locate the linked repository path?\n\n![Screenshot (701).png](https://community.atlassian.com/t5/image/serverpage/image-id/312634i22BBF4D845919BCF/image-dimensions/283x304?v=v2 \"Screenshot (701).png\")\n\nAlternatively, I am also interested in learning how to send a simple \"Hello, World!\" file, push or deploy to a remote desktop server or server using Bamboo.\n\nThank you.\n"
} | [
{
"author": "Anik Sengupta",
"body": "Hello Rizky,\n\nWelcome to Atlassian Community. Glad that you have started using Bambooa nd are finding it helpful :)\n\nThe path for the script should be either relative to the repository root of the plan, or absolute.\n\n<https://confluence.atlassian.com/bamboo/script-289277046.html>\n\n<br />\n\nThis location is known as the working directory. This is where Bamboo temporarily puts the checked-out files it's building. \nFor Bamboo8 and above - \\<BAMBOO_HOME\\>/local-working-dir/\\<JOB_KEY\\>\n\nRegarding your second query \"how to send a simple \"Hello, World!\" file to a remote desktop server using Bamboo.\"\n\nYou can use the Bamboo SCP task to upload files from Bamboo directly to a remote server as part of a Bamboo job. The SCP task is able to copy multiple files and preserves the directory structure for the copied files.\n\nMore details of the task here :- <https://confluence.atlassian.com/bamboo/using-the-scp-task-in-bamboo-305759795.html>\n\nRegards,\n\n**Anik Sengupta**\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": [
{
"author": "M Rizky Barokah",
"body": "Thanks Mr.Anik. For example, if my linked repository name is \"TestHelloWorld,\" and I want to run my helloworld.py or helloworld.java code file in the repository. where should I put it in that path?\n"
},
{
"author": "Anik Sengupta",
"body": "1. If you are using BITBUCKET make sure you first create an Application link between Bamboo and Bitbucket\n\n<https://confluence.atlassian.com/bitbucketserver/link-bitbucket-with-bamboo-1032258002.html>\n\n2. Next if you are looking to add your source code repository you need to Link a source code repository for all Bamboo plans\n\n-\\> From the Bamboo header select \\> Build resources \\> Linked repositories. \n-\\> Select Add repository. \n-\\> Select your repository type from the available menu options. For configuration details for a particular repository type, please refer to one of the following pages: \nBitbucket Cloud \nBitbucket Data Center \nGit \nGitHub (for GitHub and GitHub Enterprise) \nSubversion \nPerforce\n\nOR you can Configure a repository for a plan\n\n1. Navigate to the plan. See Configuring plans for instructions. \n2. Select Actions \\> Configure plan. \n3. Select the Repositories tab to see all the repositories that have been added to the plan. \n4. Select a repository name in the list to edit its configuration details. \n5. Select Add repository to configure a repository to be used by the plan. \nFor configuration details for a particular repository type, please refer to one of the following pages: \nBitbucket Cloud \nBitbucket Data Center \nGit \nGitHub (for GitHub and GitHub Enterprise) \nSubversion \nPerforce\n\n<br />\n\n<https://confluence.atlassian.com/bamboo/linking-to-source-code-repositories-671089223.html>\n\n3. Finally you can make use of the \"Source code checkout task\" to checkout the code from the repository. Script task is not a viable option here.\n\n<https://confluence.atlassian.com/bamboo/checking-out-code-289277060.html>\n\nLet me know if you have any further queries.\n"
},
{
"author": "M Rizky Barokah",
"body": "1. I'm trying to use the SCP Task. For example, if my linked bitbucket repository name is TestHelloWorld, and I want to send my `helloworld.txt` or any file in the repository, how should I specify it in the local path or remote path?\n\n2. I'm using Bamboo web. As I'm browsing the internet, it seems that the SCP Task requires artifacts to send. How do I produce artifacts, and which Bamboo task can produce them?\n\n![Screenshot (702).png](https://community.atlassian.com/t5/image/serverpage/image-id/312892i60182B81A3EACAFA/image-size/large?v=v2&px=999 \"Screenshot (702).png\")\n"
}
]
}
]
| https://community.atlassian.com/t5/Bamboo-questions/Send-File-to-my-Remote-Server-IP/qaq-p/2643054 | [
"bitbucket"
]
|
{
"author": "Mahesh",
"title": "My pull request is still open after merging the changes",
"body": "Hi There,\n\nI have a pull request which is reviewed and code changes are merged to develop branch, But Pull request is still open.\n\nBTW, we use bamboo plan to merge changes. Bamboo task has script that uses git squash merge commands to merge changes from feature branch to develop branch.\n\nThis issue is seen inconsistently. I most of the cases after merging the changes pull request will be closed automatically. But some times it still kept open.\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hi Mahesh,\n\nWelcome to Atlassian community.\n\nI think the first step to check will be to check the builds logs for both where the pull request is closed and where it is not, are you able to see anything different in the build logs ?\n\nRegards,\n\nShashank Kumar\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Bamboo-questions/My-pull-request-is-still-open-after-merging-the-changes/qaq-p/2635770 | [
"bitbucket",
"bitbucket-cloud",
"bitbucket-server",
"git",
"pull-request"
]
|
{
"author": "alessandro.violante",
"title": "Enabling automatic build only on build plans created by means of Pull Requests",
"body": "Hi,\n\nActually, in Bamboo, I've set the automatic creation of build plans linked to branches when I create a Pull Request for them.\n\nHowever, sometimes, I create a branch but I don't need to create a Pull Request for it, and I create its build plan manually on Bamboo.\n\nActually, regardless of how the build plans linked to branches are created (automatically by means of Pull Requests or manually without Pull Requests), when the build plan is created, a build is automatically triggered, and, with each commit, a new build is triggered.\n\nI would like to restrict the automatic builds trigger to the build plans created by means of Pull Requests.\n\nIf I create manually a build plan, I don't want that builds are automatically triggered, I want that builds are executed only manually.\n\nSomeone suggested me to use Webhooks, but I don't have enough administrative rights to configure them and at the moment I don't know anything about them.\n\nSomeone else suggested me to use the configuration I attach you in the ticket, but it doesn't work as expected.\n\nIn summary:\n\nNew branch -\\> Pull Request creation and automatic build plan creation -\\> Automatic builds\n\nNew branch -\\> Manual build plan creation -\\> Only manual builds, no automatic builds\n\nHow could this be achieved?\n\nThanks a lot in advance!\n\n![02-bamboo-branches-configuration.PNG](/t5/image/serverpage/image-id/312040i5E7C077D47BE7545/image-size/large?v=v2&px=999 \"02-bamboo-branches-configuration.PNG\")![01-bamboo-triggers-configuration.PNG](/t5/image/serverpage/image-id/312039i5EF63FD7E20C7620/image-size/large?v=v2&px=999 \"01-bamboo-triggers-configuration.PNG\")\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello [alessandro_violante](https://community.atlassian.com/t5/user/viewprofilepage/user-id/5452492),\n\nWelcome to Atlassian community.\n\nFor the branch which is created manually you'll need to change the trigger type to below.\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/312142i2F9D71E79FF8F1D8/image-size/large?v=v2&px=999 \"image.png\")\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": [
{
"author": "alessandro.violante",
"body": "Hi,\n\nThank you, is it the only way to do it or could it be done automatically for each branch created manually?\n\nI ask it because, if I use the solution you have provided me, everytime I create a new branch without creating a Pull Request, I should edit its configuration.\n\nBest regards,\n\nAlessandro\n"
},
{
"author": "Shashank Kumar",
"body": "Hello Alessandro,\n\nWhen a new Branch is created from the main(master) branch it inherits all it's properties including Triggers.\n\nYou can always set the Trigger of the main(master) branch as manual, but then the branches which are automatically created would also be having this trigger which you don't want.\n\nThe only option I can think to work with is branch override functionality, but to use that you project and plans should be managed via [Bamboo Specs](https://confluence.atlassian.com/bamboo/bamboo-specs-894743906.html) ( You cannot update those plans via GUI )\n\nif you are okay with that I guess I can provide you few options to work with, need to test few things myself.Let me know your opinion.\n\nRegards,\n\nShashank kumar\n"
},
{
"author": "alessandro.violante",
"body": "Thanks a lot, I'll ask about it and let you know!\n"
}
]
}
]
| https://community.atlassian.com/t5/Bamboo-questions/Enabling-automatic-build-only-on-build-plans-created-by-means-of/qaq-p/2639981 | null |
{
"author": "leegyu86",
"title": "Why is build workspace sometimes deleted while running?",
"body": "During execution, an error was reported saying that progress.log does not exist, as shown below.\n\nTraceback (most recent call last): \nFile \"\\<string\\>\", line 1, in \\<module\\> \nFile \"/home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2CKVEUYRA-BJT/PLAN_SCRIPT/script/process/checkout_subRepos.py\", line 35, in checkout_subRepos \nFile \"/home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2CKVEUYRA-BJT/PLAN_SCRIPT/script/common/append_description.py\", line 20, in append_description \nFileNotFoundError: \\[Errno 2\\] No such file or directory: 'progress.log'\n\nWhen I connected to the server and checked, the workspace performed by the agent had been deleted.\n\nThe agent's log was as follows.\n\nplease help\n\n<br />\n\nINFO \\| jvm 242 \\| 2024/03/09 21:29:01 \\| 2024-03-09 21:29:01,490 INFO \\[0-BAM::CICD_VEHICLE_AGENT_20::Agent:pool-5-thread-1\\] \\[TaskExecutorImpl\\] Starting task '\\[preprocess 8\\] check out sub repositories to the target revision' of type 'com.atlassian.bamboo.plugins.scripttask:task.builder.script' \nINFO \\| jvm 242 \\| 2024/03/09 21:29:01 \\| 2024-03-09 21:29:01,491 WARN \\[0-BAM::CICD_VEHICLE_AGENT_20::Agent:pool-5-thread-1\\] \\[EnvironmentVariableAccessorImpl\\] The size of environment is 9288, make sure your build environment handles this correctly \nINFO \\| jvm 242 \\| 2024/03/09 21:29:01 \\| 2024-03-09 21:29:01,492 INFO \\[0-BAM::CICD_VEHICLE_AGENT_20::Agent:pool-5-thread-1\\] \\[ProcessServiceImpl$2\\] Beginning to execute external process for build 'Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-BUILD - BUILD_JOB #2 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2CKVEUYRA-BJT-2)'\\\\n ... running command line: \\\\n/bin/sh /home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent20/temp/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2CKVEUYRA-BJT-2-ScriptBuildTask-6008075926138251910.sh\\\\n ... in: /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2CKVEUYRA-BJT\\\\n \nINFO \\| jvm 242 \\| 2024/03/09 21:29:03 \\| 2024-03-09 21:29:03,134 INFO \\[remoteEventRebroadcasterMessageListenerContainerLongLived-1\\] \\[RemoteEventRebroadcasterMessageListener\\] ExecutableQueueUpdate: addToQueue, agents known to be affected: \\[\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:30 \\| 2024-03-09 21:29:30,204 INFO \\[remoteEventRebroadcasterMessageListenerContainerLongLived-1\\] \\[RemoteEventRebroadcasterMessageListener\\] ExecutableQueueUpdate: addToQueue, agents known to be affected: \\[\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:32 \\| 2024-03-09 21:29:32,566 INFO \\[remoteEventRebroadcasterMessageListenerContainerLongLived-1\\] \\[RemoteEventRebroadcasterMessageListener\\] ExecutableQueueUpdate: addToQueue, agents known to be affected: \\[\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:32 \\| 2024-03-09 21:29:32,702 INFO \\[0-BAM::CICD_VEHICLE_AGENT_20::Agent:pool-5-thread-1\\] \\[TaskResultBuilder\\] Failing task since return code of \\[/bin/sh /home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent20/temp/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2CKVEUYRA-BJT-2-ScriptBuildTask-6008075926138251910.sh\\] was 1 while expected 0 \nINFO \\| jvm 242 \\| 2024/03/09 21:29:32 \\| 2024-03-09 21:29:32,703 INFO \\[0-BAM::CICD_VEHICLE_AGENT_20::Agent:pool-5-thread-1\\] \\[TaskExecutorImpl\\] Starting task '\\[postprocess 1\\] inform dependency' of type 'com.atlassian.bamboo.plugins.scripttask:task.builder.script' \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| 2024-03-09 21:29:38,854 ERROR \\[0-BAM::CICD_VEHICLE_AGENT_20::Agent:pool-5-thread-1\\] \\[TaskExecutorImpl\\] Error occurred while running Task '\\[postprocess 1\\] inform dependency(10)' of type com.atlassian.bamboo.plugins.scripttask:task.builder.script. \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| com.atlassian.bamboo.task.TaskException: Failed to execute task \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.plugins.shell.task.AbstractShellBuildTask.execute(AbstractShellBuildTask.java:63) \\~\\[atlassian-bamboo-plugin-scripttask-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.plugins.script.task.ScriptBuildTask.execute(ScriptBuildTask.java:66) \\~\\[atlassian-bamboo-plugin-scripttask-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.task.TaskExecutorImpl.lambda$executeTasks$3(TaskExecutorImpl.java:323) \\~\\[atlassian-bamboo-core-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.task.TaskExecutorImpl.executeTaskWithPrePostActions(TaskExecutorImpl.java:258) \\~\\[atlassian-bamboo-core-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.task.TaskExecutorImpl.executeTasks(TaskExecutorImpl.java:323) \\~\\[atlassian-bamboo-core-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.task.TaskExecutorImpl.execute(TaskExecutorImpl.java:126) \\~\\[atlassian-bamboo-core-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.build.pipeline.tasks.ExecuteBuildTask.call(ExecuteBuildTask.java:73) \\~\\[atlassian-bamboo-core-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.executeBuildPhase(DefaultBuildAgent.java:207) \\~\\[atlassian-bamboo-agent-core-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:179) \\~\\[atlassian-bamboo-agent-core-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.lambda$waitAndPerformBuild$0(BuildAgentControllerImpl.java:169) \\~\\[atlassian-bamboo-agent-core-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.variable.CustomVariableContextImpl.withVariableSubstitutor(CustomVariableContextImpl.java:118) \\~\\[atlassian-bamboo-core-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:162) \\~\\[atlassian-bamboo-agent-core-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.lambda$start$0(DefaultBuildAgent.java:124) \\~\\[atlassian-bamboo-agent-core-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:48) \\~\\[atlassian-bamboo-api-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:26) \\~\\[atlassian-bamboo-api-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:17) \\~\\[atlassian-bamboo-api-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:41) \\~\\[atlassian-bamboo-api-9.2.7.jar:?\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| at java.lang.Thread.run(Thread.java:750) \\~\\[?:1.8.0_372\\] \nINFO \\| jvm 242 \\| 2024/03/09 21:29:38 \\| Caused by: java.lang.IllegalArgumentException: The working directory /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2CKVEUYRA-BJT must exist before executing the process\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello [leegyu86](https://community.atlassian.com/t5/user/viewprofilepage/user-id/5325379),\n\nBuild workspace will be deleted if you have chosen the below option for the Jobs, but this workspace will be deleted after the Job has finished executing ( either success or Failed ) not in middle of it.\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/311472i3B0119DD6884E8F9/image-size/large?v=v2&px=999 \"image.png\")\n\nCan you explain little bit more about your scenario when did you see this error and also explain the structure of your plans.\n\nRegards,\n\nShashank Kumar\n",
"comments": [
{
"author": "leegyu86",
"body": "Sorry for the late confirmation of your reply.\n\nI checked the option you mentioned and it was Disabled.\n\nAlso I configured linux's auditd to monitor the bamboo workspace folder.\n\nStrangely enough, the AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT plan was not logged in auditd.\n\nBelow is the result of searching the plan in the bamboo log folder.\n\nThis problem is keeping me up overtime. \nPlease help me.\n\n\\[root@aescmapp04 /home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent15/logs\\]# grep -rnI AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT . \n./atlassian-bamboo.log.1:92249:2024-01-19 17:29:32,991 INFO \\[remoteEventRebroadcasterMessageListenerContainerLongLived-1\\] \\[RemoteEventRebroadcasterMessageListener\\] com.atlassian.bamboo.event.BuildDeletedEvent\\[source=null\\] job=VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT \n./atlassian-bamboo.log.1:92250:2024-01-19 17:29:32,991 INFO \\[AtlassianEvent::0-BAM::EVENTS:pool-2-thread-13\\] \\[RemoteAgentWorkspaceManagerImpl\\] Workspace VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT is no longer in use. It will be removed at the next opportunity. \n./atlassian-bamboo.log.1:473432:2024-02-17 12:36:41,827 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[RemoteAgentWorkspaceManagerImpl\\] Removing obsolete workspace for VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT \n./atlassian-bamboo.log:266532:2024-03-04 11:26:19,199 INFO \\[remoteEventRebroadcasterMessageListenerContainerLongLived-1\\] \\[RemoteEventRebroadcasterMessageListener\\] com.atlassian.bamboo.event.BuildDeletedEvent\\[source=null\\] job=VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT \n./atlassian-bamboo.log:266533:2024-03-04 11:26:19,199 INFO \\[AtlassianEvent::0-BAM::EVENTS:pool-2-thread-3\\] \\[RemoteAgentWorkspaceManagerImpl\\] Workspace VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT is no longer in use. It will be removed at the next opportunity. \n./atlassian-bamboo.log:268663:2024-03-04 12:52:19,146 INFO \\[remoteEventRebroadcasterMessageListenerContainerLongLived-1\\] \\[RemoteEventRebroadcasterMessageListener\\] com.atlassian.bamboo.event.BuildDeletedEvent\\[source=null\\] job=VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT \n./atlassian-bamboo.log:268664:2024-03-04 12:52:19,146 INFO \\[AtlassianEvent::0-BAM::EVENTS:pool-2-thread-7\\] \\[RemoteAgentWorkspaceManagerImpl\\] Workspace VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT is no longer in use. It will be removed at the next opportunity. \n./atlassian-bamboo.log:271530:2024-03-04 12:58:55,489 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[RemoteAgentWorkspaceManagerImpl\\] Removing obsolete workspace for VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT \n./atlassian-bamboo.log:277931:2024-03-04 13:19:38,988 INFO \\[remoteEventRebroadcasterMessageListenerContainerLongLived-1\\] \\[RemoteEventRebroadcasterMessageListener\\] com.atlassian.bamboo.event.BuildDeletedEvent\\[source=null\\] job=VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT \n./atlassian-bamboo.log:277932:2024-03-04 13:19:38,988 INFO \\[AtlassianEvent::0-BAM::EVENTS:pool-2-thread-9\\] \\[RemoteAgentWorkspaceManagerImpl\\] Workspace VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT is no longer in use. It will be removed at the next opportunity. \n./atlassian-bamboo.log:282167:2024-03-04 16:02:20,869 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[RemoteAgentWorkspaceManagerImpl\\] Removing obsolete workspace for VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT \n./atlassian-bamboo.log:391174:2024-03-09 20:51:03,808 INFO \\[remoteEventRebroadcasterMessageListenerContainerLongLived-1\\] \\[RemoteEventRebroadcasterMessageListener\\] com.atlassian.bamboo.event.BuildDeletedEvent\\[source=null\\] job=VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT \n./atlassian-bamboo.log:391175:2024-03-09 20:51:03,808 INFO \\[AtlassianEvent::0-BAM::EVENTS:pool-2-thread-7\\] \\[RemoteAgentWorkspaceManagerImpl\\] Workspace VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT is no longer in use. It will be removed at the next opportunity. \n./atlassian-bamboo.log:392281:2024-03-09 23:14:35,663 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[RemoteAgentWorkspaceManagerImpl\\] Removing obsolete workspace for VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT \n./atlassian-bamboo.log:463755:2024-03-13 22:16:53,295 INFO \\[remoteEventRebroadcasterMessageListenerContainerLongLived-1\\] \\[RemoteEventRebroadcasterMessageListener\\] com.atlassian.bamboo.event.BuildDeletedEvent\\[source=null\\] job=VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT \n./atlassian-bamboo.log:463756:2024-03-13 22:16:53,295 INFO \\[AtlassianEvent::0-BAM::EVENTS:pool-2-thread-4\\] \\[RemoteAgentWorkspaceManagerImpl\\] Workspace VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT is no longer in use. It will be removed at the next opportunity. \n./atlassian-bamboo.log:463774:2024-03-13 22:22:07,815 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[BuildAgentControllerImpl\\] Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1) taken from queue. \n./atlassian-bamboo.log:463775:2024-03-13 22:22:07,831 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[RemoteExecutionPhaseServiceImpl\\] Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1) assigned to agent 156139573 \n./atlassian-bamboo.log:463776:2024-03-13 22:22:07,848 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[DefaultBuildAgent\\] Changing context: null -\\> VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1 on CICD_VEHICLE_AGENT_15/6f962245 \n./atlassian-bamboo.log:463777:2024-03-13 22:22:07,900 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[BuildAgentControllerImpl\\] Build Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1) is being prepared for building on agent CICD_VEHICLE_AGENT_15, bamboo version: 9.2.7 \n./atlassian-bamboo.log:463780:2024-03-13 22:22:07,901 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[RemoteExecutionPhaseServiceImpl\\] Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1) VCS sync started \n./atlassian-bamboo.log:463781:2024-03-13 22:22:07,935 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[CheckoutDirectoriesSnapshotHelper\\] Build working directory is /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT \n./atlassian-bamboo.log:463783:2024-03-13 22:22:07,936 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[PrepareBuildTask\\] Executing build Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1) \n./atlassian-bamboo.log:463785:2024-03-13 22:22:07,937 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[CleanWorkingDirectoryTask\\] Cleaning working directory '/home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT' \n./atlassian-bamboo.log:463789:2024-03-13 22:22:07,939 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[PrepareBuildTask\\] Build Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1) started building on agent 'CICD_VEHICLE_AGENT_15' (Remote agent on aescmapp04 CICD_VEHICLE_AGENT_15) \n./atlassian-bamboo.log:463791:2024-03-13 22:22:07,939 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[ExecuteBuildTask\\] Starting execution: VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1, logger: 1214825463 \n./atlassian-bamboo.log:463792:2024-03-13 22:22:07,939 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[RemoteExecutionPhaseServiceImpl\\] Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1) execution started \n./atlassian-bamboo.log:463795:2024-03-13 22:22:07,977 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[ProcessServiceImpl$2\\] Beginning to execute external process for build 'Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1)'\\\\n ... running command line: \\\\n/bin/sh /home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent15/temp/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1-ScriptBuildTask-5027392812213069454.sh\\\\n ... in: /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT\\\\n \n./atlassian-bamboo.log:463798:2024-03-13 22:22:20,338 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[ProcessServiceImpl$2\\] Beginning to execute external process for build 'Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1)'\\\\n ... running command line: \\\\n/bin/sh /home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent15/temp/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1-ScriptBuildTask-2921917006128431442.sh\\\\n ... in: /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT\\\\n \n./atlassian-bamboo.log:463801:2024-03-13 22:22:21,340 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[ProcessServiceImpl$2\\] Beginning to execute external process for build 'Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1)'\\\\n ... running command line: \\\\n/home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent15/temp/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1-ScriptBuildTask-9156185043247633936.sh\\\\n ... in: /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT\\\\n \n./atlassian-bamboo.log:463804:2024-03-13 22:22:22,129 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[ProcessServiceImpl$2\\] Beginning to execute external process for build 'Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1)'\\\\n ... running command line: \\\\n/home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent15/temp/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1-ScriptBuildTask-2718954282654229122.sh\\\\n ... in: /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT\\\\n \n./atlassian-bamboo.log:463808:2024-03-13 22:22:22,465 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[ProcessServiceImpl$2\\] Beginning to execute external process for build 'Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1)'\\\\n ... running command line: \\\\n/home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent15/temp/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1-ScriptBuildTask-5391568561020502893.sh\\\\n ... in: /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT\\\\n \n./atlassian-bamboo.log:463811:2024-03-13 22:22:26,792 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[ProcessServiceImpl$2\\] Beginning to execute external process for build 'Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1)'\\\\n ... running command line: \\\\n/home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent15/temp/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1-ScriptBuildTask-1871788283120142199.sh\\\\n ... in: /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT\\\\n \n./atlassian-bamboo.log:463815:2024-03-13 22:23:25,430 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[ProcessServiceImpl$2\\] Beginning to execute external process for build 'Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1)'\\\\n ... running command line: \\\\n/bin/sh /home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent15/temp/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1-ScriptBuildTask-646330145406559475.sh\\\\n ... in: /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT\\\\n \n./atlassian-bamboo.log:463819:2024-03-13 22:23:57,819 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[TaskResultBuilder\\] Failing task since return code of \\[/bin/sh /home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent15/temp/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1-ScriptBuildTask-646330145406559475.sh\\] was 1 while expected 0 \n./atlassian-bamboo.log:463841:Caused by: java.lang.IllegalArgumentException: The working directory /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT must exist before executing the process \n./atlassian-bamboo.log:463869:Caused by: java.lang.IllegalArgumentException: The working directory /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT must exist before executing the process \n./atlassian-bamboo.log:463897:Caused by: java.lang.IllegalArgumentException: The working directory /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT must exist before executing the process \n./atlassian-bamboo.log:463914:2024-03-13 22:24:04,717 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[BuildArtifactPostProcessor\\] Copying the build artifacts for build: VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1 \n./atlassian-bamboo.log:463915:2024-03-13 22:24:04,717 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[RemoteExecutionPhaseServiceImpl\\] Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1) execution finished \n./atlassian-bamboo.log:463916:2024-03-13 22:24:04,749 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[AbstractArtifactManager\\] Publishing \\[LogsFromBambooAgent\\] for VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1: 1 file(s) matching \\[plan-172955907-RJT-1.log\\] in directory /home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent15/temp/log_spool, excluding \\[\\] \n./atlassian-bamboo.log:463921:2024-03-13 22:24:04,827 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[RemoteResultProcessor\\] Build Vehicle Electronics SW - SCM-MCU_SG2_EV-MCU_SG2_EV-PR-62-RV - REQUIREMENT_JOB #1 (VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1) completed on Bamboo agent. Sending results to server. \n./atlassian-bamboo.log:463924:2024-03-13 22:24:04,907 INFO \\[0-BAM::CICD_VEHICLE_AGENT_15::Agent:pool-5-thread-1\\] \\[DefaultBuildAgent\\] Changing context: VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2SKY-RJT-1 -\\> null on CICD_VEHICLE_AGENT_15/6f962245\n"
},
{
"author": "Shashank Kumar",
"body": "Hello [leegyu86,](https://community.atlassian.com/t5/user/viewprofilepage/user-id/5325379)\n\nCan you provide the build working directory of your agent ? this information can be seen in bamboo-agent.cfg.xml file under \\<buildWorkingDirectory\\</buildWorkingDirectory\\> properties.\n\nAlso in your script task what values you have in your **Working subdirectory**values, can you recheck if that's correct ?\n\nRegards,\n\nShashank Kumar\n"
},
{
"author": "leegyu86",
"body": "I'm sorry for checking back so late. I will definitely check the alarm.\n\n<br />\n\nBelow is the result of outputting the configuration file using the cat command.\n\nworking subdirectory is blank\n\n\\[root@aescmapp04 /home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent15\\]# cat bamboo-agent.cfg.xml \n\\<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"no\"?\\> \n\\<configuration\\> \n\\<buildWorkingDirectory\\>/home/cicd_vehicle/bamboo_agent_home/WORKSPACE\\</buildWorkingDirectory\\> \n\\<agentUuid\\>2f43e4a5-50e8-4e70-8976-5b685f92e9fe\\</agentUuid\\> \n\\<agentDefinition\\> \n\\<id\\>156139573\\</id\\> \n\\<name\\>CICD_VEHICLE_AGENT_15\\</name\\> \n\\<description\\>Remote agent on aescmapp04 CICD_VEHICLE_AGENT_15\\</description\\> \n\\</agentDefinition\\> \n\\</configuration\\>\n\n<br />\n\n\\[root@aescmapp04 /home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent15\\]# cat conf/wrapper.conf \\| grep -E -i '\\^\\[\\^#\\]' \nwrapper.java.command=/usr/bin/java \nwrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp \nwrapper.java.classpath.1=../lib/wrapper.jar \nwrapper.java.classpath.2=../lib/bamboo-agent-bootstrap.jar \nwrapper.java.library.path.1=../lib \nwrapper.java.additional.1=-Dbamboo.home=/home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent15 \nwrapper.java.additional.2=-Dbamboo.agent.ignoreServerCertName=false \nwrapper.java.additional.3=-Dbamboo.allow.empty.artifacts=false \nwrapper.java.additional.5=-Dsun.jnu.encoding=utf-8 \nwrapper.java.additional.4=-Dfile.encoding=utf-8 \nwrapper.app.parameter.1=com.atlassian.bamboo.agent.bootstrap.AgentBootstrap \nwrapper.app.parameter.2=<https://bamboo.autoever.com/agentServer/> \nwrapper.app.parameter.3= \nwrapper.on_exit.0=SHUTDOWN \nwrapper.on_exit.default=RESTART \nwrapper.java.initmemory=256 \nwrapper.java.maxmemory=1024 \nwrapper.working.dir=. \nwrapper.console.format=LPTM \nwrapper.console.loglevel=INFO \nwrapper.console.flush=true \nwrapper.logfile=../atlassian-bamboo-agent.log \nwrapper.logfile.format=LPTM \nwrapper.logfile.loglevel=INFO \nwrapper.logfile.maxsize=10m \nwrapper.logfile.maxfiles=10 \nwrapper.syslog.loglevel=INFO \nwrapper.successful_invocation_time=3 \nwrapper.max_failed_invocations=1440 \nwrapper.console.title=Bamboo Remote Agent \nwrapper.java.version.min=8 \nwrapper.java.version.max=11 \nwrapper.java.version.fallback=8 \nwrapper.name=bamboo-remote-agent \nwrapper.displayname=Bamboo Remote Agent \nwrapper.description=A remote agent for building Bamboo build plans. \nwrapper.ntservice.starttype=AUTO_START \nwrapper.ntservice.interactive=FALSE\n"
},
{
"author": "leegyu86",
"body": "The following events were confirmed with auditd.\n\ntime-\\>Mon Mar 18 14:21:25 2024 \ntype=PROCTITLE msg=audit(1710739285.943:7626410): proctitle=2F7573722F6C69622F6A766D2F6A6176612D312E382E302D6F70656E6A646B2D312E382E302E3337322E6230372D312E656C385F372E7838365F36342F6A72652F62696E2F6A617661002D4462616D626F6F2E686F6D653D2F686F6D652F636963645F76656869636C652F62616D626F6F5F6167656E745F686F6D652F636963 \ntype=PATH msg=audit(1710739285.943:7626410): item=1 name=\"/home/cicd_vehicle/bamboo_agent_home/WORKSPACE/repositoryData/VES-AIVIDEP2FKAZF6TKDKVPU2SKHKJAVISKPJZPTETSEH5SGK5TFNRXXAP2UIMZTQN27JVBVKP2CKVEUYRA-MJT.xml\" inode=36044903 dev=08:00 mode=0100644 ouid=1003 ogid=1004 rdev=00:00 nametype=DELETE cap_fp=0 cap_fi=0 cap_fe=0 cap_fver=0 cap_frootid=0 \ntype=PATH msg=audit(1710739285.943:7626410): item=0 name=\"/home/cicd_vehicle/bamboo_agent_home/WORKSPACE/repositoryData/\" inode=36044801 dev=08:00 mode=040755 ouid=1003 ogid=1004 rdev=00:00 nametype=PARENT cap_fp=0 cap_fi=0 cap_fe=0 cap_fver=0 cap_frootid=0 \ntype=CWD msg=audit(1710739285.943:7626410): cwd=\"/home/cicd_vehicle/bamboo_agent_home/cicd_vehicle_agent06/bin\" \ntype=SYSCALL msg=audit(1710739285.943:7626410): arch=c000003e syscall=87 success=yes exit=0 a0=7f14c81ee0b0 a1=7f14c8000cd8 a2=0 a3=6 items=2 ppid=2389 pid=3620998 auid=4294967295 uid=1003 gid=1004 euid=1003 suid=1003 fsuid=1003 egid=1004 sgid=1004 fsgid=1004 tty=(none) ses=4294967295 comm=\"0-BAM::CICD_VEH\" exe=\"/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.372.b07-1.el8_7.x86_64/jre/bin/java\" key=\"scm_event\"\n"
},
{
"author": "Shashank Kumar",
"body": "Hello ,\n\nYour Build directory is **/home/cicd_vehicle/bamboo_agent_home/WORKSPACE**\n\ninitial build directory which you highlighted /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2CKVEUYRA-BJT/PLAN_SCRIPT/script/process/checkout_subRepos.py\n\nHere VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2CKVEUYRA-BJT will be your Job key.\n\nIdeally even if the build fails as per your setting /home/cicd_vehicle/bamboo_agent_home/WORKSPACE/VES-AKNBU2P2NINKV6U2HGJPUKVR7MRSXMZLMN5YD6TKDKVPVGRZSL5CVMP2CKVEUYRA-BJT directory should not be deleted.\n\nAt this point I am not clear what is the issue, even the audit logs which you have pasted is not for this folder.\n\nYou can try few thing like try to disable all the task and enable them one by one and run the build and try to identify in which task the build fails and the directory gets deleted, this will give you some idea to fix it.\n\nAt this stage I think it will be better if you can raise a ticket with Bamboo support team where this can be checked better.\n"
}
]
}
]
| https://community.atlassian.com/t5/Bamboo-questions/Why-is-build-workspace-sometimes-deleted-while-running/qaq-p/2635034 | null |
{
"author": "accelQ",
"title": "Migrating to AMPS 8.1.2 got banned dependency. Is there a way to resolve this, from dependency tree",
"body": "Banned Deps:\n\nFound Banned Dependency: org.slf4j:slf4j-api:jar:1.7.36 \nFound Banned Dependency: org.apache.httpcomponents:httpclient:jar:4.5.13 \nFound Banned Dependency: org.apache.httpcomponents:httpcore:jar:4.4.13 \n\n<br />\n\ndependency Tree: \n\ncom.aq:aqconnect:atlassian-plugin:1.0.8 \n\\[INFO\\] +- com.atlassian.bamboo:atlassian-bamboo-web:jar:6.8.0:provided \n\\[INFO\\] \\| +- com.atlassian.bamboo:atlassian-bamboo-core:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.bamboo:atlassian-bamboo-api:jar:6.8.0:provided \n\\[INFO\\] \\| \\| \\| +- com.atlassian.bamboo:atlassian-bamboo-api-agent-bootstrap:jar:6.8.0:provided \n\\[INFO\\] \\| \\| \\| +- com.atlassian.extras:atlassian-extras-api:jar:3.3.0:provided \n\\[INFO\\] \\| \\| \\| +- com.atlassian.config:atlassian-config:jar:1.0.1:provided \n\\[INFO\\] \\| \\| \\| +- com.atlassian.plugins:atlassian-plugins-webfragment-api:jar:4.0.0:provided \n\\[INFO\\] \\| \\| \\| +- com.atlassian.bandana:atlassian-bandana:jar:3.1:provided \n\\[INFO\\] \\| \\| \\| +- com.atlassian.cache:atlassian-cache-api:jar:2.11.3:provided \n\\[INFO\\] \\| \\| \\| \\| +- com.atlassian.bundles:jsr305:jar:1.1:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- com.atlassian.instrumentation:atlassian-instrumentation-core:jar:2.2.1:provided \n\\[INFO\\] \\| \\| \\| +- org.apache.ant:ant:jar:1.8.4:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- org.apache.ant:ant-launcher:jar:1.8.4:provided \n\\[INFO\\] \\| \\| \\| +- org.apache.commons:commons-text:jar:1.1:provided \n\\[INFO\\] \\| \\| \\| +- commons-configuration:commons-configuration:jar:1.4-atlassian-1:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- commons-jxpath:commons-jxpath:jar:1.2:provided \n\\[INFO\\] \\| \\| \\| +- commons-beanutils:commons-beanutils:jar:1.9.3:provided \n\\[INFO\\] \\| \\| \\| +- com.atlassian.seraph:atlassian-seraph:jar:4.0.2:provided \n\\[INFO\\] \\| \\| \\| +- opensymphony:osuser:jar:1.0-20060106:provided \n\\[INFO\\] \\| \\| \\| +- org.acegisecurity:acegi-security:jar:1.0.4:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- oro:oro:jar:2.0.8:provided \n\\[INFO\\] \\| \\| \\| +- net.jcip:jcip-annotations:jar:1.0:provided \n\\[INFO\\] \\| \\| \\| +- com.atlassian.soy:soy-template-renderer-plugin-api:jar:4.0.4:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- com.atlassian.soy:soy-template-renderer-api:jar:4.0.4:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.fusesource.jansi:jansi:jar:1.11:provided \n\\[INFO\\] \\| \\| +- com.atlassian.bamboo:atlassian-bamboo-deployments-api:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.bamboo:bamboo-specs:jar:6.8.0:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.google.code.findbugs:jsr305:jar:3.0.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.bamboo:atlassian-bamboo-core-agent-bootstrap:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.bamboo:atlassian-bamboo-utils:jar:6.8.0:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.jsoup:jsoup:jar:1.10.2:provided \n\\[INFO\\] \\| \\| +- com.atlassian.bamboo:atlassian-bamboo-xml-utils:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.analytics:analytics-api:jar:5.6.1:provided \n\\[INFO\\] \\| \\| +- com.atlassian.bamboo.security.classlist:security-classlist-api:jar:1.0.1:provided \n\\[INFO\\] \\| \\| +- com.atlassian.bonnie:atlassian-bonnie:jar:6.1-lucene4.6-1:provided \n\\[INFO\\] \\| \\| \\| +- org.apache.lucene:lucene-analyzers-common:jar:4.6.0:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.ibm.icu:icu4j:jar:3.8:provided \n\\[INFO\\] \\| \\| +- com.atlassian.cache:atlassian-cache-ehcache:jar:2.11.3:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.atlassian.cache:atlassian-cache-common-impl:jar:2.11.3:provided \n\\[INFO\\] \\| \\| +- com.atlassian.collectors:atlassian-collectors-util:jar:0.10:provided \n\\[INFO\\] \\| \\| +- com.atlassian.ip:atlassian-ip:jar:3.1:provided \n\\[INFO\\] \\| \\| +- com.atlassian.plugins:atlassian-plugins-core:jar:4.1.0:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.atlassian.plugins:atlassian-plugins-api:jar:4.1.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.plugins:atlassian-plugins-spring:jar:4.1.0:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.springframework:spring-web:jar:4.1.7.RELEASE:provided \n\\[INFO\\] \\| \\| +- com.atlassian.plugins:atlassian-plugins-webfragment:jar:4.0.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.security:atlassian-secure-random:jar:3.2.4:provided \n\\[INFO\\] \\| \\| +- com.atlassian.security:atlassian-secure-xml:jar:3.2.4:provided \n\\[INFO\\] \\| \\| +- com.atlassian.security.auth.trustedapps:atlassian-trusted-apps-seraph-integration:jar:4.1.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.security.auth.trustedapps:atlassian-trusted-apps-core:jar:4.1.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.spring:atlassian-spring:jar:2.0.7:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.springframework:spring-jdbc:jar:2.0.6:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.springframework:spring-dao:jar:2.0.6:provided \n\\[INFO\\] \\| \\| +- com.atlassian.utils:atlassian-processutils:jar:1.7.9:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.jvnet.winp:winp:jar:1.17-atlassian1:provided \n\\[INFO\\] \\| \\| +- com.atlassian.velocity:atlassian-velocity:jar:0.5:provided \n\\[INFO\\] \\| \\| +- com.sun.xml.bind:jaxb-core:jar:2.2.11:provided \n\\[INFO\\] \\| \\| +- org.apache.commons:commons-collections4:jar:4.2:provided \n\\[INFO\\] \\| \\| +- commons-lang:commons-lang:jar:2.6:provided \n\\[INFO\\] \\| \\| +- commons-validator:commons-validator:jar:1.6:provided \n\\[INFO\\] \\| \\| +- commons-httpclient:commons-httpclient:jar:3.1-atlassian-2:provided \n\\[INFO\\] \\| \\| +- dom4j:dom4j:jar:1.6.1:provided \n\\[INFO\\] \\| \\| +- jaxen:jaxen:jar:1.1.6:provided \n\\[INFO\\] \\| \\| +- javacvs:javacvs:jar:atlassian-20080407:provided \n\\[INFO\\] \\| \\| +- org.apache.commons:commons-lang3:jar:3.7:provided \n\\[INFO\\] \\| \\| +- org.springframework:spring-jms:jar:5.0.8.RELEASE:provided \n\\[INFO\\] \\| \\| \\| +- org.springframework:spring-messaging:jar:5.0.8.RELEASE:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.springframework:spring-tx:jar:5.0.8.RELEASE:provided \n\\[INFO\\] \\| \\| +- org.springframework:spring-context-support:jar:5.0.8.RELEASE:provided \n\\[INFO\\] \\| \\| +- com.tek42.perforce:p4java:jar:0.7.5-atlassian-13:provided \n\\[INFO\\] \\| \\| +- commons-digester:commons-digester:jar:2.1:provided \n\\[INFO\\] \\| \\| +- org.aspectj:aspectjrt:jar:1.9.1:provided \n\\[INFO\\] \\| \\| +- org.aspectj:aspectjweaver:jar:1.9.1:provided \n\\[INFO\\] \\| \\| +- org.hibernate:hibernate-jpamodelgen:jar:5.3.4.Final:provided \n\\[INFO\\] \\| \\| +- cglib:cglib-nodep:jar:2.2:provided \n\\[INFO\\] \\| \\| +- com.sun.mail:javax.mail:jar:1.5.2:provided \n\\[INFO\\] \\| \\| +- org.igniterealtime.smack:smack-core:jar:4.1.9:provided \n\\[INFO\\] \\| \\| \\| +- xpp3:xpp3:jar:1.1.4c:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.jxmpp:jxmpp-core:jar:0.4.2:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.jxmpp:jxmpp-util-cache:jar:0.4.2:provided \n\\[INFO\\] \\| \\| +- org.igniterealtime.smack:smack-tcp:jar:4.1.9:provided \n\\[INFO\\] \\| \\| +- joda-time:joda-time:jar:2.8.2:provided \n\\[INFO\\] \\| \\| +- log4j:log4j:jar:1.2.17:provided \n\\[INFO\\] \\| \\| +- org.quartz-scheduler:quartz:jar:2.2.3:provided \n\\[INFO\\] \\| \\| +- org.tmatesoft.svnkit:svnkit:jar:1.8.15:provided \n\\[INFO\\] \\| \\| \\| +- de.regnis.q.sequence:sequence-library:jar:1.0.3:provided \n\\[INFO\\] \\| \\| \\| +- org.tmatesoft.sqljet:sqljet:jar:1.1.10:provided \n\\[INFO\\] \\| \\| \\| +- net.java.dev.jna:jna:jar:4.1.0:provided \n\\[INFO\\] \\| \\| \\| +- net.java.dev.jna:jna-platform:jar:4.1.0:provided \n\\[INFO\\] \\| \\| \\| +- com.trilead:trilead-ssh2:jar:1.0.0-build221:provided \n\\[INFO\\] \\| \\| \\| +- com.jcraft:jsch.agentproxy.connector-factory:jar:0.0.7:provided \n\\[INFO\\] \\| \\| \\| \\| +- com.jcraft:jsch.agentproxy.core:jar:0.0.7:provided \n\\[INFO\\] \\| \\| \\| \\| +- com.jcraft:jsch.agentproxy.usocket-jna:jar:0.0.7:provided \n\\[INFO\\] \\| \\| \\| \\| \\| \\\\- net.java.dev.jna:platform:jar:3.4.0:provided \n\\[INFO\\] \\| \\| \\| \\| +- com.jcraft:jsch.agentproxy.usocket-nc:jar:0.0.7:provided \n\\[INFO\\] \\| \\| \\| \\| +- com.jcraft:jsch.agentproxy.sshagent:jar:0.0.7:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- com.jcraft:jsch.agentproxy.pageant:jar:0.0.7:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.jcraft:jsch.agentproxy.svnkit-trilead-ssh2:jar:0.0.7:provided \n\\[INFO\\] \\| \\| +- com.jcraft:jsch:jar:0.1.54:provided \n\\[INFO\\] \\| \\| +- velocity:velocity:jar:1.4:provided \n\\[INFO\\] \\| \\| +- com.thoughtworks.xstream:xstream:jar:1.4.10:provided \n\\[INFO\\] \\| \\| \\| \\\\- xmlpull:xmlpull:jar:1.1.3.1:provided \n\\[INFO\\] \\| \\| +- com.thoughtworks.xstream:xstream-hibernate:jar:1.4.10:provided \n\\[INFO\\] \\| \\| +- org.apache.lucene:lucene-core:jar:4.6.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian:lucene-filtered-collector:jar:4.6.1:provided \n\\[INFO\\] \\| \\| +- com.atlassian.mail:atlassian-mail:jar:2.7.19:provided \n\\[INFO\\] \\| \\| \\| +- javax.mail:javax.mail-api:jar:1.5.6:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.atlassian:atlassian-localhost:jar:1.1.0:provided \n\\[INFO\\] \\| \\| +- org.apache.activemq:activemq-broker:jar:5.14.5:provided \n\\[INFO\\] \\| \\| \\| +- org.apache.activemq:activemq-client:jar:5.14.5:provided \n\\[INFO\\] \\| \\| \\| \\| +- org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.1.1:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- org.fusesource.hawtbuf:hawtbuf:jar:1.11:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.apache.activemq:activemq-openwire-legacy:jar:5.14.5:provided \n\\[INFO\\] \\| \\| +- org.apache.xbean:xbean-spring:jar:3.2:provided \n\\[INFO\\] \\| \\| +- org.apache.sshd:sshd-core:jar:1.7.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.botocss:botocss:jar:3.0:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.antlr:antlr-runtime:jar:3.4:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.antlr:stringtemplate:jar:3.2.1:provided \n\\[INFO\\] \\| \\| +- org.scala-lang:scala-library:jar:2.10.3:provided \n\\[INFO\\] \\| \\| +- com.tdunning:t-digest:jar:3.2:provided \n\\[INFO\\] \\| \\| +- com.atlassian.plugins:atlassian-plugins-webresource:jar:3.3.7:provided \n\\[INFO\\] \\| \\| \\| +- com.atlassian.plugins:atlassian-plugins-webresource-api:jar:3.3.7:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.atlassian.sourcemap:sourcemap:jar:1.7.2:provided \n\\[INFO\\] \\| \\| +- com.atlassian.plugins:atlassian-plugins-webresource-common:jar:4.1.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.fugue:fugue:jar:2.7.0:provided \n\\[INFO\\] \\| \\| +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.1:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.codehaus.jackson:jackson-core-asl:jar:1.9.1:provided \n\\[INFO\\] \\| \\| +- com.atlassian.crowd:embedded-crowd-spi:jar:3.2.4:provided \n\\[INFO\\] \\| \\| +- com.atlassian.crowd:embedded-crowd-api:jar:3.2.4:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.crowd:embedded-crowd-core:jar:3.2.4:provided \n\\[INFO\\] \\| \\| +- com.atlassian.crowd:crowd-events:jar:3.2.4:provided \n\\[INFO\\] \\| \\| +- com.atlassian.crowd:crowd-ldap:jar:3.2.4:provided \n\\[INFO\\] \\| \\| \\| +- com.atlassian.crowd:crowd-synchronisation:jar:3.2.4:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.springframework.ldap:spring-ldap-core:jar:2.2.1.RELEASE:provided \n\\[INFO\\] \\| \\| +- com.atlassian.crowd:crowd-azure-ad:jar:3.2.4:provided \n\\[INFO\\] \\| \\| \\| +- com.nimbusds:nimbus-jose-jwt:jar:4.38:provided \n\\[INFO\\] \\| \\| \\| +- com.nimbusds:lang-tag:jar:1.4.3:provided \n\\[INFO\\] \\| \\| \\| +- net.minidev:json-smart:jar:1.3.1:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.microsoft.azure:adal4j:jar:1.2.0:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.nimbusds:oauth2-oidc-sdk:jar:5.18.1:provided \n\\[INFO\\] \\| \\| +- com.atlassian.crowd:crowd-remote:jar:3.2.4:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.atlassian.crowd:crowd-integration-client-rest:jar:3.2.4:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.apache.httpcomponents:httpclient-cache:jar:4.5.3:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.crowd:crowd-core-tiny:jar:3.2.4:provided \n\\[INFO\\] \\| +- com.atlassian.bamboo:atlassian-bamboo-persistence:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.user:atlassian-user-hibernate3:jar:5.4.14:provided \n\\[INFO\\] \\| \\| \\| +- com.atlassian.security:atlassian-password-encoder:jar:3.0:provided \n\\[INFO\\] \\| \\| \\| +- com.opensymphony.propertyset:core:jar:1.6.0-atlassian-8:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.opensymphony.propertyset.providers:hibernate5:jar:1.6.0-atlassian-8:provided \n\\[INFO\\] \\| \\| +- org.springframework:spring-orm:jar:5.0.8.RELEASE:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.crowd:crowd-persistence-hibernate5:jar:3.2.4-hibernate53-1:provided \n\\[INFO\\] \\| \\| +- com.atlassian.crowd:crowd-persistence:jar:3.2.4:provided \n\\[INFO\\] \\| \\| +- com.google.code.findbugs:findbugs-annotations:jar:3.0.1:provided \n\\[INFO\\] \\| \\| +- com.atlassian.hibernate:atlassian-hibernate5.2-extras:jar:6.1.1:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.crowd:crowd-server-api:jar:3.2.4:provided \n\\[INFO\\] \\| +- com.atlassian.bamboo:atlassian-bamboo-migration:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.activeobjects:activeobjects-spi:jar:1.2.3:provided \n\\[INFO\\] \\| \\| +- org.codehaus.woodstox:atlassian-wstx-core-asl:jar:4.1.2-atlassian-1:provided \n\\[INFO\\] \\| \\| \\\\- org.codehaus.staxmate:staxmate:jar:2.0.0:provided \n\\[INFO\\] \\| \\| \\\\- org.codehaus.woodstox:stax2-api:jar:3.0.4:provided (version selected from constraint \\[3.0.0,3.1.0)) \n\\[INFO\\] \\| +- com.atlassian.bamboo:atlassian-bamboo-language:jar:6.8.0:provided \n\\[INFO\\] \\| +- com.atlassian.bamboo:atlassian-bamboo-charts:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- jfree:jfreechart:jar:1.0.9:provided \n\\[INFO\\] \\| \\| \\\\- jfree:jcommon:jar:1.0.12:provided \n\\[INFO\\] \\| +- com.atlassian.bamboo:atlassian-bamboo-upgrader:jar:6.8.0:provided \n\\[INFO\\] \\| +- com.atlassian.bamboo:atlassian-bamboo-license:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.extras:atlassian-extras-core:jar:3.3.0:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.atlassian.extras:atlassian-extras-decoder-v2:jar:3.3.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.extras:atlassian-extras-common:jar:3.3.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.extras:atlassian-extras-legacy:jar:3.3.0:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.atlassian.extras:atlassian-extras-decoder-api:jar:3.3.0:provided \n\\[INFO\\] \\| \\| +- io.atlassian.fugue:fugue:jar:3.0.0:provided \n\\[INFO\\] \\| \\| \\\\- xpp3:xpp3_min:jar:1.1.4c:provided \n\\[INFO\\] \\| +- com.atlassian.bamboo:atlassian-bamboo-agent-classserver:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.bamboo:atlassian-bamboo-agent-remote:jar:6.8.0:provided \n\\[INFO\\] \\| \\| \\| +- org.apache.activemq:activemq-pool:jar:5.14.5:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- org.apache.activemq:activemq-jms-pool:jar:5.14.5:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.esotericsoftware:kryo:jar:3.0.3:provided \n\\[INFO\\] \\| \\| \\| +- com.esotericsoftware:reflectasm:jar:1.10.1:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- org.ow2.asm:asm:jar:5.0.3:provided \n\\[INFO\\] \\| \\| \\| +- com.esotericsoftware:minlog:jar:1.3.0:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.objenesis:objenesis:jar:2.1:provided \n\\[INFO\\] \\| \\| +- com.atlassian.bamboo:atlassian-bamboo-agent-bootstrap:jar:6.8.0:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.slf4j:jcl-over-slf4j:jar:1.7.10:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.bamboo:atlassian-bamboo-agent-elastic:jar:6.8.0:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.aws:atlassian-aws-bootstrap:jar:1.0.170:provided \n\\[INFO\\] \\| +- com.atlassian.bamboo:atlassian-bamboo-agent-local:jar:6.8.0:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.bamboo:atlassian-bamboo-agent-core:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.bamboo.plugins:atlassian-bamboo-plugin-ssh:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- org.apache.activemq:activemq-ra:jar:5.14.5:provided \n\\[INFO\\] \\| \\| \\| +- org.apache.activemq:activemq-kahadb-store:jar:5.14.5:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.apache.geronimo.specs:geronimo-j2ee-connector_1.5_spec:jar:2.0.0:provided \n\\[INFO\\] \\| \\| \\\\- org.apache.geronimo.components:geronimo-transaction:jar:3.1:provided \n\\[INFO\\] \\| \\| +- org.apache.geronimo.specs:geronimo-jta_1.1_spec:jar:1.1.1:provided \n\\[INFO\\] \\| \\| \\\\- org.apache.geronimo.specs:geronimo-j2ee-connector_1.6_spec:jar:1.0:provided \n\\[INFO\\] \\| +- com.atlassian.bamboo:atlassian-bamboo-agent-elastic-server:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.aws:atlassian-aws:jar:1.0.170:provided \n\\[INFO\\] \\| \\| \\| +- com.amazonaws:aws-java-sdk-core:jar:1.11.394:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- software.amazon.ion:ion-java:jar:1.0.2:provided \n\\[INFO\\] \\| \\| \\| +- com.amazonaws:aws-java-sdk-ec2:jar:1.11.394:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- com.amazonaws:jmespath-java:jar:1.11.394:provided \n\\[INFO\\] \\| \\| \\| +- com.amazonaws:aws-java-sdk-s3:jar:1.11.394:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- com.amazonaws:aws-java-sdk-kms:jar:1.11.394:provided \n\\[INFO\\] \\| \\| \\| +- com.amazonaws:aws-java-sdk-codedeploy:jar:1.11.394:provided \n\\[INFO\\] \\| \\| \\| +- com.amazonaws:aws-java-sdk-iam:jar:1.11.394:provided \n\\[INFO\\] \\| \\| \\| +- org.bouncycastle:bcpkix-jdk15on:jar:1.59:provided \n\\[INFO\\] \\| \\| \\| +- com.fasterxml.jackson.core:jackson-databind:jar:2.8.10:provided \n\\[INFO\\] \\| \\| \\| \\| +- com.fasterxml.jackson.core:jackson-annotations:jar:2.8.0:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- com.fasterxml.jackson.core:jackson-core:jar:2.8.10:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:2.8.10:provided \n\\[INFO\\] \\| \\| +- com.atlassian.bamboo:atlassian-bamboo-agent-elastic-shared:jar:6.8.0:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.tunnel:atlassian-tunnel:jar:1.8.8:provided \n\\[INFO\\] \\| +- com.atlassian.bamboo:atlassian-bamboo-maven-embedder:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- org.jetbrains:annotations:jar:13.0:provided \n\\[INFO\\] \\| \\| +- org.apache.maven:maven-core:jar:3.0.5:provided \n\\[INFO\\] \\| \\| \\| +- org.apache.maven:maven-settings-builder:jar:3.0.5:provided \n\\[INFO\\] \\| \\| \\| +- org.apache.maven:maven-repository-metadata:jar:3.0.5:provided \n\\[INFO\\] \\| \\| \\| +- org.apache.maven:maven-artifact:jar:3.0.5:provided \n\\[INFO\\] \\| \\| \\| +- org.apache.maven:maven-aether-provider:jar:3.0.5:provided \n\\[INFO\\] \\| \\| \\| +- org.sonatype.aether:aether-impl:jar:1.13.1:provided \n\\[INFO\\] \\| \\| \\| +- org.sonatype.aether:aether-api:jar:1.13.1:provided \n\\[INFO\\] \\| \\| \\| +- org.sonatype.aether:aether-util:jar:1.13.1:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.codehaus.plexus:plexus-interpolation:jar:1.14:provided \n\\[INFO\\] \\| \\| +- com.google.inject:guice:jar:4.0:provided \n\\[INFO\\] \\| \\| \\| \\\\- aopalliance:aopalliance:jar:1.0:provided \n\\[INFO\\] \\| \\| +- org.sonatype.aether:aether-connector-wagon:jar:1.13.1:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.sonatype.aether:aether-spi:jar:1.13.1:provided \n\\[INFO\\] \\| \\| +- org.apache.maven.wagon:wagon-provider-api:jar:2.4:provided \n\\[INFO\\] \\| \\| +- org.apache.maven.wagon:wagon-file:jar:2.4:provided \n\\[INFO\\] \\| \\| \\\\- org.apache.maven.wagon:wagon-http:jar:2.4:provided \n\\[INFO\\] \\| \\| \\\\- org.apache.maven.wagon:wagon-http-shared4:jar:2.4:provided \n\\[INFO\\] \\| +- com.atlassian.bamboo:atlassian-bamboo-import-export:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- org.yaml:snakeyaml:jar:1.18:provided \n\\[INFO\\] \\| \\| +- com.atlassian.bamboo:bamboo-specs-api:jar:6.8.0:provided \n\\[INFO\\] \\| \\| \\\\- com.spotify:docker-client:jar:shaded:8.11.7:provided \n\\[INFO\\] \\| +- com.atlassian.bamboo:atlassian-embedded-crowd-atlassian-user:jar:6.8.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.bucket:atlassian-bucket:jar:5.1.6:provided \n\\[INFO\\] \\| \\| +- com.atlassian.crowd:crowd-integration-seraph:jar:3.2.4:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.atlassian.crowd:crowd-integration-client-common:jar:3.2.4:provided \n\\[INFO\\] \\| \\| +- com.atlassian.crowd:crowd-api:jar:3.2.4:provided \n\\[INFO\\] \\| \\| +- com.atlassian.crowd:crowd-core:jar:3.2.4:provided \n\\[INFO\\] \\| \\| \\| +- com.atlassian.crowd:crowd-password-encoders:jar:3.2.4:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- org.springframework.security:spring-security-core:jar:4.2.4.RELEASE:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.atlassian.crowd:crowd-server-common:jar:3.2.4:provided \n\\[INFO\\] \\| \\| +- com.atlassian.crowd:crowd-integration-api:jar:3.2.4:provided \n\\[INFO\\] \\| \\| +- com.atlassian.user:atlassian-user-api:jar:5.4.14:provided \n\\[INFO\\] \\| \\| \\| \\\\- com.opensymphony.propertyset:api:jar:1.6.0-atlassian-8:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.user:atlassian-user-core:jar:5.4.14:provided \n\\[INFO\\] \\| +- com.atlassian:webwork-compat:jar:1.33:provided \n\\[INFO\\] \\| \\| \\\\- javax.servlet:javax.servlet-api:jar:3.0.1:provided \n\\[INFO\\] \\| +- com.atlassian.applinks:applinks-api:jar:5.4.12:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.annotations:atlassian-annotations:jar:0.16:provided \n\\[INFO\\] \\| +- com.atlassian.applinks:applinks-host:jar:5.4.12:provided \n\\[INFO\\] \\| +- com.atlassian.applinks:applinks-spi:jar:5.4.12:provided \n\\[INFO\\] \\| +- com.atlassian.beehive:beehive-api:jar:0.2.1:provided \n\\[INFO\\] \\| +- com.atlassian.beehive:beehive-single-node:jar:0.2.1:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.beehive:beehive-core:jar:0.2.1:provided \n\\[INFO\\] \\| +- com.atlassian.core:atlassian-core:jar:5.0.2:provided \n\\[INFO\\] \\| \\| +- com.google.guava:guava:jar:10.0.1:provided \n\\[INFO\\] \\| \\| +- commons-collections:commons-collections:jar:3.1:provided \n\\[INFO\\] \\| \\| +- commons-logging:commons-logging:jar:1.0.4:compile \n\\[INFO\\] \\| \\| +- opensymphony:oscore:jar:2.2.7:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.image:atlassian-image-consumer:jar:1.0.1:provided \n\\[INFO\\] \\| +- com.atlassian.html:atlassian-html-encoder:jar:1.5:provided \n\\[INFO\\] \\| +- com.atlassian.http:atlassian-http:jar:2.0.2:provided \n\\[INFO\\] \\| +- com.atlassian.json:atlassian-json-api:jar:0.9:provided \n\\[INFO\\] \\| +- com.atlassian.johnson:atlassian-johnson-core:jar:3.5.0:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.plugins:atlassian-plugins-servlet:jar:3.2.8:provided \n\\[INFO\\] \\| +- com.atlassian.plugins:atlassian-plugins-schema:jar:4.1.0:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.plugins:atlassian-plugins-osgi:jar:4.1.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.plugins:atlassian-plugins-osgi-events:jar:4.1.0:provided \n\\[INFO\\] \\| \\| +- biz.aQute.bnd:biz.aQute.bndlib:jar:2.4.1:provided \n\\[INFO\\] \\| \\| +- org.apache.felix:org.apache.felix.framework:jar:4.2.1:provided \n\\[INFO\\] \\| \\| \\\\- org.twdata.pkgscanner:package-scanner:jar:0.9.5:provided \n\\[INFO\\] \\| +- com.atlassian.profiling:atlassian-profiling:jar:1.9:provided \n\\[INFO\\] \\| +- com.atlassian.sal:sal-api:jar:3.0.8:provided \n\\[INFO\\] \\| +- com.atlassian.sal:sal-spi:jar:3.0.8:provided \n\\[INFO\\] \\| +- com.atlassian.sal:sal-spring:jar:3.0.8:provided \n\\[INFO\\] \\| +- com.atlassian.sal:sal-trust-api:jar:3.0.8:provided \n\\[INFO\\] \\| +- com.atlassian.scheduler:atlassian-scheduler-api:jar:1.6.0:provided \n\\[INFO\\] \\| +- com.atlassian.scheduler:atlassian-scheduler-core:jar:1.6.0:provided \n\\[INFO\\] \\| +- com.atlassian.scheduler:atlassian-scheduler-quartz2:jar:1.6.0:provided \n\\[INFO\\] \\| \\| \\\\- org.quartz-scheduler:quartz-oracle:jar:2.1.7:provided \n\\[INFO\\] \\| +- com.atlassian.security:atlassian-secure-utils:jar:3.2.4:provided \n\\[INFO\\] \\| +- com.atlassian.tenancy:atlassian-tenancy-api:jar:2.0.0:provided \n\\[INFO\\] \\| \\| +- com.atlassian.util.concurrent:atlassian-util-concurrent:jar:2.4.1:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.event:atlassian-event:jar:2.3.2:provided \n\\[INFO\\] \\| +- com.atlassian.xwork:atlassian-xwork-12:jar:2.5.10-struts-2:provided \n\\[INFO\\] \\| \\| \\\\- com.atlassian.xwork:atlassian-xwork-core:jar:2.5.10-struts-2:provided \n\\[INFO\\] \\| +- io.atlassian.util.concurrent:atlassian-util-concurrent:jar:4.0.0:provided \n\\[INFO\\] \\| +- com.h2database:h2:jar:1.4.194:provided \n\\[INFO\\] \\| +- org.apache.activemq:activemq-http:jar:5.14.5-atlassian-1:provided \n\\[INFO\\] \\| \\| +- org.apache.activemq:activemq-spring:jar:5.14.5:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.apache.commons:commons-pool2:jar:2.4.2:provided \n\\[INFO\\] \\| \\| +- org.apache.activemq:activemq-stomp:jar:5.14.5:provided \n\\[INFO\\] \\| \\| +- org.apache.activemq:activemq-mqtt:jar:5.14.5:provided \n\\[INFO\\] \\| \\| \\| +- org.apache.activemq.protobuf:activemq-protobuf:jar:1.1:provided \n\\[INFO\\] \\| \\| \\| +- org.fusesource.mqtt-client:mqtt-client:jar:1.14:provided \n\\[INFO\\] \\| \\| \\| +- org.fusesource.hawtdispatch:hawtdispatch-transport:jar:1.22:provided \n\\[INFO\\] \\| \\| \\| \\| \\\\- org.fusesource.hawtdispatch:hawtdispatch:jar:1.22:provided \n\\[INFO\\] \\| \\| \\| +- org.apache.geronimo.specs:geronimo-j2ee-management_1.1_spec:jar:1.0.1:provided \n\\[INFO\\] \\| \\| \\| \\\\- commons-net:commons-net:jar:3.5:provided \n\\[INFO\\] \\| \\| \\\\- org.eclipse.jetty.aggregate:jetty-all:jar:9.2.13.v20150730:provided \n\\[INFO\\] \\| +- org.hibernate:hibernate-core:jar:5.3.4.Final-atlassian-6:provided \n\\[INFO\\] \\| \\| +- org.jboss.logging:jboss-logging:jar:3.3.2.Final:provided \n\\[INFO\\] \\| \\| +- javax.persistence:javax.persistence-api:jar:2.2:provided \n\\[INFO\\] \\| \\| +- org.javassist:javassist:jar:3.23.1-GA:provided \n\\[INFO\\] \\| \\| +- net.bytebuddy:byte-buddy:jar:1.8.15:provided \n\\[INFO\\] \\| \\| +- antlr:antlr:jar:2.7.7:provided \n\\[INFO\\] \\| \\| +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.1.1.Final:provided \n\\[INFO\\] \\| \\| +- org.jboss:jandex:jar:2.0.5.Final:provided \n\\[INFO\\] \\| \\| +- com.fasterxml:classmate:jar:1.3.4:provided \n\\[INFO\\] \\| \\| +- javax.activation:javax.activation-api:jar:1.2.0:provided \n\\[INFO\\] \\| \\| \\\\- org.hibernate.common:hibernate-commons-annotations:jar:5.0.4.Final:provided \n\\[INFO\\] \\| +- org.hibernate:hibernate-c3p0:jar:5.3.4.Final:provided \n\\[INFO\\] \\| +- org.hibernate:hibernate-ehcache:jar:5.3.4.Final:provided \n\\[INFO\\] \\| \\| \\\\- net.sf.ehcache:ehcache:jar:2.10.3:provided \n\\[INFO\\] \\| +- org.slf4j:jul-to-slf4j:jar:1.7.10:provided \n\\[INFO\\] \\| +- org.slf4j:slf4j-log4j12:jar:1.7.10:provided \n\\[INFO\\] \\| +- org.springframework:spring-beans:jar:5.0.8.RELEASE:provided \n\\[INFO\\] \\| +- org.springframework:spring-context:jar:5.0.8.RELEASE:provided \n\\[INFO\\] \\| \\| +- org.springframework:spring-aop:jar:5.0.8.RELEASE:provided \n\\[INFO\\] \\| \\| \\\\- org.springframework:spring-expression:jar:5.0.8.RELEASE:provided \n\\[INFO\\] \\| +- org.springframework:spring-core:jar:5.0.8.RELEASE:provided \n\\[INFO\\] \\| \\| \\\\- org.springframework:spring-jcl:jar:5.0.8.RELEASE:provided \n\\[INFO\\] \\| +- rome:rome:jar:1.0:provided \n\\[INFO\\] \\| +- com.mchange:c3p0:jar:0.9.5.2:provided \n\\[INFO\\] \\| \\| \\\\- com.mchange:mchange-commons-java:jar:0.2.11:provided \n\\[INFO\\] \\| +- de.schlichtherle.truezip:truezip-file:jar:7.7.10:provided \n\\[INFO\\] \\| \\| +- de.schlichtherle.truezip:truezip-driver-file:jar:7.7.10:provided \n\\[INFO\\] \\| \\| \\\\- de.schlichtherle.truezip:truezip-kernel:jar:7.7.10:provided \n\\[INFO\\] \\| +- de.schlichtherle.truezip:truezip-driver-zip:jar:7.7.10:provided \n\\[INFO\\] \\| \\| +- de.schlichtherle.truezip:truezip-swing:jar:7.7.10:provided \n\\[INFO\\] \\| \\| +- org.apache.commons:commons-compress:jar:1.9:provided \n\\[INFO\\] \\| \\| \\\\- org.bouncycastle:bcprov-jdk15on:jar:1.52:provided \n\\[INFO\\] \\| +- jdom:jdom:jar:1.0:provided \n\\[INFO\\] \\| +- javax.transaction:jta:jar:1.0.1B:provided \n\\[INFO\\] \\| +- com.github.ziplet:ziplet:jar:2.1.2:provided \n\\[INFO\\] \\| +- org.apache.struts:struts2-core:jar:2.5.17-atlassian-1:provided \n\\[INFO\\] \\| \\| +- ognl:ognl:jar:3.1.15:provided \n\\[INFO\\] \\| \\| \\\\- org.apache.logging.log4j:log4j-api:jar:2.10.0:provided \n\\[INFO\\] \\| +- org.freemarker:freemarker:jar:2.3.24-atlassian-20:provided \n\\[INFO\\] \\| \\| +- logkit:logkit:jar:1.2:provided \n\\[INFO\\] \\| \\| \\\\- com.google.code.findbugs:annotations:jar:3.0.0:provided \n\\[INFO\\] \\| +- opensymphony:sitemesh:jar:2.5-atlassian-6:provided \n\\[INFO\\] \\| +- commons-fileupload:commons-fileupload:jar:1.3.3:provided \n\\[INFO\\] \\| +- org.tuckey:urlrewritefilter:jar:4.0.3:provided \n\\[INFO\\] \\| +- velocity-tools:velocity-tools:jar:1.2:provided \n\\[INFO\\] \\| +- org.hamcrest:hamcrest-all:jar:1.3:provided \n\\[INFO\\] \\| +- javax.xml.stream:stax-api:jar:1.0-2:provided \n\\[INFO\\] \\| +- org.apache.maven:maven-embedder:jar:3.0.5:provided \n\\[INFO\\] \\| \\| +- org.apache.maven:maven-settings:jar:3.0.5:provided \n\\[INFO\\] \\| \\| +- org.apache.maven:maven-plugin-api:jar:3.0.5:provided \n\\[INFO\\] \\| \\| +- org.apache.maven:maven-model-builder:jar:3.0.5:provided \n\\[INFO\\] \\| \\| +- org.apache.maven:maven-compat:jar:3.0.5:provided \n\\[INFO\\] \\| \\| +- org.codehaus.plexus:plexus-utils:jar:2.0.6:provided \n\\[INFO\\] \\| \\| +- org.codehaus.plexus:plexus-classworlds:jar:2.4:provided \n\\[INFO\\] \\| \\| +- org.sonatype.sisu:sisu-inject-plexus:jar:2.3.0:provided \n\\[INFO\\] \\| \\| \\| \\\\- org.sonatype.sisu:sisu-inject-bean:jar:2.3.0:provided \n\\[INFO\\] \\| \\| +- org.codehaus.plexus:plexus-component-annotations:jar:1.5.5:provided \n\\[INFO\\] \\| \\| +- org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3:provided \n\\[INFO\\] \\| \\| +- org.sonatype.plexus:plexus-cipher:jar:1.7:provided \n\\[INFO\\] \\| \\| \\\\- commons-cli:commons-cli:jar:1.2:provided \n\\[INFO\\] \\| +- org.apache.maven:maven-model:jar:3.0.5:provided \n\\[INFO\\] \\| +- com.octo.captcha:jcaptcha:jar:2.0-alpha-1:provided \n\\[INFO\\] \\| +- com.octo.captcha:jcaptcha-api:jar:2.0-alpha-1:provided \n\\[INFO\\] \\| +- com.jhlabs:filters:jar:2.0.235:provided \n\\[INFO\\] \\| +- org.apache.struts:struts2-sitemesh-plugin:jar:2.1.8.1:provided \n\\[INFO\\] \\| +- org.apache.logging.log4j:log4j-to-slf4j:jar:2.7:provided \n\\[INFO\\] \\| +- org.apache.httpcomponents:httpmime:jar:4.5.5:provided \n\\[INFO\\] \\| +- org.reflections:reflections:jar:0.9.10:provided \n\\[INFO\\] \\| \\\\- xerces:xercesImpl:jar:2.11.0:provided \n\\[INFO\\] \\| \\\\- xml-apis:xml-apis:jar:1.4.01:provided \n\\[INFO\\] +- com.atlassian.plugin:atlassian-spring-scanner-annotation:jar:1.2.13:compile \n\\[INFO\\] +- com.atlassian.plugin:atlassian-spring-scanner-runtime:jar:1.2.13:runtime \n\\[INFO\\] +- javax.inject:javax.inject:jar:1:provided \n\\[INFO\\] +- junit:junit:jar:4.10:test \n\\[INFO\\] \\| \\\\- org.hamcrest:hamcrest-core:jar:1.1:provided \n\\[INFO\\] +- com.atlassian.plugins:atlassian-plugins-osgi-testrunner:jar:1.2.3:test \n\\[INFO\\] \\| +- org.apache.wink:wink-client:jar:1.1.3-incubating:test \n\\[INFO\\] \\| \\| +- org.apache.wink:wink-common:jar:1.1.3-incubating:test \n\\[INFO\\] \\| \\| \\| \\\\- org.apache.geronimo.specs:geronimo-annotation_1.1_spec:jar:1.0:test \n\\[INFO\\] \\| \\| +- javax.xml.bind:jaxb-api:jar:2.2:test \n\\[INFO\\] \\| \\| +- com.sun.xml.bind:jaxb-impl:jar:2.2.1.1:test \n\\[INFO\\] \\| \\| \\\\- javax.activation:activation:jar:1.1:test \n\\[INFO\\] \\| +- commons-io:commons-io:jar:1.4:provided \n\\[INFO\\] \\| +- com.google.code.gson:gson:jar:2.2.2-atlassian-1:provided \n\\[INFO\\] \\| \\\\- com.atlassian.upm:upm-api:jar:2.15:test \n\\[INFO\\] +- javax.ws.rs:jsr311-api:jar:1.1.1:provided \n\\[INFO\\] +- com.googlecode.json-simple:json-simple:jar:1.1.1:compile \n\\[INFO\\] +- org.apache.httpcomponents.client5:httpclient5:jar:5.3.1:compile \n\\[INFO\\] \\| +- org.apache.httpcomponents.core5:httpcore5:jar:5.2.4:compile \n\\[INFO\\] \\| +- org.apache.httpcomponents.core5:httpcore5-h2:jar:5.2.4:compile \n\\[INFO\\] \\| \\\\- org.slf4j:slf4j-api:jar:1.7.36:compile \n\\[INFO\\] +- org.apache.avalon.framework:avalon-framework-impl:jar:4.3.1:compile \n\\[INFO\\] \\| \\\\- org.apache.avalon.framework:avalon-framework-api:jar:4.3.1:compile \n\\[INFO\\] \\\\- core:aqCore:jar:1.0:compile \n\\[INFO\\] +- commons-codec:commons-codec:jar:1.10:compile \n\\[INFO\\] \\\\- org.apache.httpcomponents:httpclient:jar:4.5.13:compile \n\\[INFO\\] \\\\- org.apache.httpcomponents:httpcore:jar:4.4.13:compile \n\n<br />\n\nPOM file \n\n\\<?xml version=\"1.0\" encoding=\"UTF-8\"?\\>\n\n\\<project xmlns=\"<http://maven.apache.org/POM/4.0.0>\" \nxmlns:xsi=\"<http://www.w3.org/2001/XMLSchema-instance>\" \nxsi:schemaLocation=\"<http://maven.apache.org/POM/4.0.0> <http://maven.apache.org/maven-v4_0_0.xsd>\"\\>\n\n\\<modelVersion\\>4.0.0\\</modelVersion\\> \n\\<groupId\\>com.aq\\</groupId\\> \n\\<artifactId\\>aqconnect\\</artifactId\\> \n\\<version\\>1.0.8\\</version\\>\n\n\\<organization\\> \n\\<name\\>ACCELQ\\</name\\> \n\\<url\\><http://www.accelq.com/>\\</url\\> \n\\</organization\\>\n\n\\<name\\>aqconnect\\</name\\> \n\\<description\\>ACCELQ Continuous Integration\\</description\\> \n\\<packaging\\>atlassian-plugin\\</packaging\\>\n\n\\<properties\\> \n\\<bamboo.version\\>6.8.0\\</bamboo.version\\> \n\\<bamboo.data.version\\>6.8.0\\</bamboo.data.version\\> \n\\<amps.version\\>8.1.2\\</amps.version\\> \n\\<plugin.testrunner.version\\>1.2.3\\</plugin.testrunner.version\\> \n\\<atlassian.spring.scanner.version\\>1.2.13\\</atlassian.spring.scanner.version\\> \n\\<!-- This key is used to keep the consistency between the key in atlassian-plugin.xml and the key to generate bundle. --\\> \n\\<atlassian.plugin.key\\>${project.groupId}.${project.artifactId}\\</atlassian.plugin.key\\> \n\\<!-- \\<extn\\>jar\\</extn\\> --\\> \n\\</properties\\>\n\n\\<dependencies\\> \n\\<dependency\\> \n\\<groupId\\>com.atlassian.bamboo\\</groupId\\> \n\\<artifactId\\>atlassian-bamboo-web\\</artifactId\\> \n\\<version\\>${bamboo.version}\\</version\\> \n\\<scope\\>provided\\</scope\\> \n\\</dependency\\>\n\n\\<dependency\\> \n\\<groupId\\>com.atlassian.plugin\\</groupId\\> \n\\<artifactId\\>atlassian-spring-scanner-annotation\\</artifactId\\> \n\\<version\\>${atlassian.spring.scanner.version}\\</version\\> \n\\<scope\\>compile\\</scope\\> \n\\</dependency\\>\n\n\\<dependency\\> \n\\<groupId\\>com.atlassian.plugin\\</groupId\\> \n\\<artifactId\\>atlassian-spring-scanner-runtime\\</artifactId\\> \n\\<version\\>${atlassian.spring.scanner.version}\\</version\\> \n\\<scope\\>runtime\\</scope\\> \n\\</dependency\\> \n\\<dependency\\> \n\\<groupId\\>javax.inject\\</groupId\\> \n\\<artifactId\\>javax.inject\\</artifactId\\> \n\\<version\\>1\\</version\\> \n\\<scope\\>provided\\</scope\\> \n\\</dependency\\> \n\\<dependency\\> \n\\<groupId\\>junit\\</groupId\\> \n\\<artifactId\\>junit\\</artifactId\\> \n\\<version\\>4.10\\</version\\> \n\\<scope\\>test\\</scope\\> \n\\</dependency\\>\n\n\\<!-- WIRED TEST RUNNER DEPENDENCIES --\\> \n\\<dependency\\> \n\\<groupId\\>com.atlassian.plugins\\</groupId\\> \n\\<artifactId\\>atlassian-plugins-osgi-testrunner\\</artifactId\\> \n\\<version\\>${plugin.testrunner.version}\\</version\\> \n\\<scope\\>test\\</scope\\> \n\\</dependency\\> \n\\<dependency\\> \n\\<groupId\\>javax.ws.rs\\</groupId\\> \n\\<artifactId\\>jsr311-api\\</artifactId\\> \n\\<version\\>1.1.1\\</version\\> \n\\<scope\\>provided\\</scope\\> \n\\</dependency\\> \n\\<dependency\\> \n\\<groupId\\>com.googlecode.json-simple\\</groupId\\> \n\\<artifactId\\>json-simple\\</artifactId\\> \n\\<version\\>1.1.1\\</version\\> \n\\</dependency\\> \n\\<!-- <https://mvnrepository.com/artifact/org.apache.httpcomponents.client5/httpclient5> --\\> \n\\<dependency\\> \n\\<groupId\\>org.apache.httpcomponents.client5\\</groupId\\> \n\\<artifactId\\>httpclient5\\</artifactId\\> \n\\<version\\>5.3.1\\</version\\> \n\\</dependency\\> \n\\<dependency\\> \n\\<groupId\\>org.apache.avalon.framework\\</groupId\\> \n\\<artifactId\\>avalon-framework-impl\\</artifactId\\> \n\\<version\\>4.3.1\\</version\\> \n\\</dependency\\> \n\\<dependency\\> \n\\<groupId\\>core\\</groupId\\> \n\\<artifactId\\>aqCore\\</artifactId\\> \n\\<!-- \\<scope\\>system\\</scope\\>--\\> \n\\<version\\>1.0\\</version\\> \n\\<!-- \\<systemPath\\>${pom.baseUri}/src/lib/core-1.0-SNAPSHOT.jar\\</systemPath\\>--\\> \n\\</dependency\\> \n\\</dependencies\\>\n\n\\<build\\> \n\\<plugins\\> \n\\<plugin\\> \n\\<groupId\\>com.atlassian.maven.plugins\\</groupId\\> \n\\<artifactId\\>bamboo-maven-plugin\\</artifactId\\> \n\\<version\\>${amps.version}\\</version\\> \n\\<extensions\\>true\\</extensions\\> \n\\<configuration\\> \n\\<productVersion\\>${bamboo.version}\\</productVersion\\> \n\\<productDataVersion\\>${bamboo.data.version}\\</productDataVersion\\> \n\\<enableQuickReload\\>true\\</enableQuickReload\\> \n\\<enableFastdev\\>false\\</enableFastdev\\>\n\n\\<!-- See here for an explanation of default instructions: --\\> \n\\<!-- <https://developer.atlassian.com/docs/advanced-topics/configuration-of-instructions-in-atlassian-plugins> --\\> \n\\<instructions\\> \n\\<Atlassian-Plugin-Key\\>${atlassian.plugin.key}\\</Atlassian-Plugin-Key\\>\n\n\\<!-- Add package to export here --\\> \n\\<Export-Package\\> \ncom.example.api, \n\\</Export-Package\\>\n\n\\<!-- Add package import here --\\> \n\\<Import-Package\\> \norg.springframework.osgi.\\*;resolution:=\"optional\", \norg.eclipse.gemini.blueprint.\\*;resolution:=\"optional\", \n\\* \n\\</Import-Package\\>\n\n\\<!-- Ensure plugin is spring powered --\\> \n\\<Spring-Context\\>\\*\\</Spring-Context\\> \n\\</instructions\\> \n\\</configuration\\> \n\\</plugin\\>\n\n\\<plugin\\> \n\\<groupId\\>com.atlassian.plugin\\</groupId\\> \n\\<artifactId\\>atlassian-spring-scanner-maven-plugin\\</artifactId\\> \n\\<version\\>${atlassian.spring.scanner.version}\\</version\\> \n\\<executions\\> \n\\<execution\\> \n\\<goals\\> \n\\<goal\\>atlassian-spring-scanner\\</goal\\> \n\\</goals\\> \n\\<phase\\>process-classes\\</phase\\> \n\\</execution\\> \n\\</executions\\> \n\\<configuration\\> \n\\<scannedDependencies\\> \n\\<dependency\\> \n\\<groupId\\>com.atlassian.plugin\\</groupId\\> \n\\<artifactId\\>atlassian-spring-scanner-external-jar\\</artifactId\\> \n\\</dependency\\> \n\\</scannedDependencies\\> \n\\<verbose\\>false\\</verbose\\> \n\\</configuration\\> \n\\</plugin\\> \n\\</plugins\\> \n\\</build\\> \n\\<repositories\\> \n\\<repository\\> \n\\<id\\>atlassian-public\\</id\\> \n\\<url\\><https://maven.atlassian.com/repository/public>\\</url\\> \n\\<snapshots\\> \n\\<enabled\\>true\\</enabled\\> \n\\<updatePolicy\\>never\\</updatePolicy\\> \n\\<checksumPolicy\\>warn\\</checksumPolicy\\> \n\\</snapshots\\> \n\\<releases\\> \n\\<enabled\\>true\\</enabled\\> \n\\<checksumPolicy\\>warn\\</checksumPolicy\\> \n\\</releases\\> \n\\</repository\\> \n\\<repository\\> \n\\<id\\>atlassian-plugin-sdk\\</id\\> \n\\<url\\>file://${env.ATLAS_HOME}/repository\\</url\\> \n\\<snapshots\\> \n\\<enabled\\>true\\</enabled\\> \n\\</snapshots\\> \n\\<releases\\> \n\\<enabled\\>true\\</enabled\\> \n\\<checksumPolicy\\>warn\\</checksumPolicy\\> \n\\</releases\\> \n\\</repository\\> \n\\</repositories\\> \n\\<pluginRepositories\\> \n\\<pluginRepository\\> \n\\<id\\>atlassian-public\\</id\\> \n\\<url\\><https://maven.atlassian.com/repository/public>\\</url\\> \n\\<releases\\> \n\\<enabled\\>true\\</enabled\\> \n\\<checksumPolicy\\>warn\\</checksumPolicy\\> \n\\</releases\\> \n\\<snapshots\\> \n\\<updatePolicy\\>never\\</updatePolicy\\> \n\\<checksumPolicy\\>warn\\</checksumPolicy\\> \n\\</snapshots\\> \n\\</pluginRepository\\> \n\\<pluginRepository\\> \n\\<id\\>atlassian-plugin-sdk\\</id\\> \n\\<url\\>file://${env.ATLAS_HOME}/repository\\</url\\> \n\\<releases\\> \n\\<enabled\\>true\\</enabled\\> \n\\<checksumPolicy\\>warn\\</checksumPolicy\\> \n\\</releases\\> \n\\<snapshots\\> \n\\<enabled\\>true\\</enabled\\> \n\\</snapshots\\> \n\\</pluginRepository\\> \n\\</pluginRepositories\\> \n\\</project\\>\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello [accelQ](https://community.atlassian.com/t5/user/viewprofilepage/user-id/5220429).\n\nWelcome to Atlassian community.\n\nI believe your answer is covered in this article \\> <https://community.developer.atlassian.com/t/more-info-on-amps-banned-plugin-dependency/46036/4>\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Bamboo-questions/Migrating-to-AMPS-8-1-2-got-banned-dependency-Is-there-a-way-to/qaq-p/2634214 | null |
{
"author": "Peter Drexel",
"title": "Bamboo detached HEAD",
"body": "Regarding the detached HEAD message that sometimes appears in the Bamboo build logs, is there a configuration option that will trigger a failure of the build when this occurs or is there a way to detect that this has occurred so that we know the build is not legit? For the latter, I'm thinking about programmatically \"looking\" at the build log, \"seeing\" detached HEAD message and forcing a failure.\n"
} | [
{
"author": "Eduardo Alvarenga",
"body": "Hello **[@Peter Drexel](/t5/user/viewprofilepage/user-id/5382479),**\n\nBamboo will not fail the build in case of a detached HEAD because whenever you rerun a build that is based on a commit revision that is not the HEAD any longer, it should continue normally.\n\nIn your case, if you'd like to avoid that you can add a script task that will check if the current checked-out tree is not in a HEAD state and fail it if so. For example:\n\n```\n#!/bin/bash\n\n# Check if we are in a git repository\nif git rev-parse --git-dir > /dev/null 2>&1; then\n # Check if HEAD is detached\n if git status | grep -q 'HEAD detached'; then\n echo \"ERROR: The current checked out code is in a detached HEAD state.\"\n exit 127\n else\n echo \"HEAD is attached. All is good.\"\n fi\nelse\n echo \"This is not a Git repository.\"\nfi\n```\n\nBy adding the steps above after the checkout task, Bamboo will validate if the checked out code is in a HEAD state and exit with a \"127\" error code in case it is. You can pick the error code you want.\n\nThank you,\n\nEduardo Alvarenga \nAtlassian Support APAC\n\n**--please don't forget to Accept the answer if the reply is helpful--**\n",
"comments": [
{
"author": "Peter Drexel",
"body": "Hi Eduardo, thanks for the quick response. Can I use this script in Windows too or do I need to make some modifications?\n"
},
{
"author": "Eduardo Alvarenga",
"body": "Hi [@Peter Drexel](/t5/user/viewprofilepage/user-id/5382479)\n\nYou can certainly run in Windows If the Agent has some type of runtime engine such as Cygwin to interpret the bash script. Some recent versions of Windows will support bash natively.\n\nOtherwise, I suggest you migrate the logic to Powershell or Windows Batch language.\n\nThank you,\n\nEduardo Alvarenga\n\nAtlassian Support APAC\n\n**--please don't forget to Accept the answer if the reply is helpful--**\n"
}
]
}
]
| https://community.atlassian.com/t5/Bamboo-questions/Bamboo-detached-HEAD/qaq-p/2632154 | null |
{
"author": "naghma_parween",
"title": "Is xcresult file type not supported as bamboo artifact?",
"body": "Hi,\n\nI am running a fastlane build for my iOS application on bamboo. I am trying to save filetype \".xcresult\" as a build artifact. \nThis file is present at the provided location but not attached as a build artifact. \nI also tried to return all files present in the folder as an artifact. However, apart from xcresult file, the other file, in the said folder, was attached as build artifact. \n\nDoes that mean, bamboo does not support this file type as an artifact? \nIs there a list of supported/un-supported file type for artifact? \n\nPlease let me know. Thank you!\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello Naghma,\n\nWelcome to Atlassian Support\n\nAs far as I am aware Bamboo does not have any limitation on file types as Artifacts, just for testing purpose I defined a artifact and using generated a test file using **touch abcd.xcresult**in my script task, I am able to see this file in the artifacts tab, below is my artifact definition.\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/312927iAB476CF8449FF067/image-size/large?v=v2&px=999 \"image.png\")\n\nYou can see my artifact was created and I am able to download it\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/312928i351FAE9746874A42/image-size/large?v=v2&px=999 \"image.png\")\n\nCan you try the above artifact definition and let me know the results.\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": [
{
"author": "naghma_parween",
"body": "Hi [Shashank Kumar](https://community.atlassian.com/t5/user/viewprofilepage/user-id/4693340) , \nI have tried this way of declaration and couple of other ways too that I could think of but it didn't work out for me. \nIf not for the extension type will the name of the file be a problem? ![screenshot.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/312952i2230968CD1F7BF29/image-size/large?v=v2&px=999 \"screenshot.PNG\") The file name is long and has .-+ symbols in it.\n"
},
{
"author": "naghma_parween",
"body": "Just an update, I tried fetching the file after shortening the name without any special chars, it didn't work. \nHowever, it worked when I converted the file to a zip file. \nJust for my curiosity, is there any way to restrict bamboo on the instance level regarding the type of file bamboo attaches as an artifact? \nIt might be that the restriction is on my organization's bamboo.\n"
},
{
"author": "Shashank Kumar",
"body": "Hello Naghma,\n\nOn Instance level we don't have a functionality to restrict Bamboo to read the artifacts, the only way this can be done is on **each** **Artifact** level using **Exclusion pattern(s)**\n\n**![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/313002iDE466BAADC0CB865/image-size/large?v=v2&px=999 \"image.png\")**\n\nBamboo normally ignores any hidden files for artifacts which are inside the folder, but I believe that is not the case with you.\n\nWhat is the Bamboo version you are using, I'll try to see If I am able to replicate the issue and maybe it can be a bug on that version, also please send me the exact pattern of the file and it's name and size.\n\nRegards,\n\nShashank Kumar\n"
},
{
"author": "naghma_parween",
"body": "Hi [Shashank Kumar](https://community.atlassian.com/t5/user/viewprofilepage/user-id/4693340) \n\nThe bamboo version I am using is version 9.4.1 build 90412. \nIt's not a hidden file and the user has read-write access to it. I reconfirmed. \n\nPlease see the attached pictures, for .xcresult.zip file, I am able to get artifact attachment. \nWhile when I change the file pattern to .xcresult file, I am not getting any attachments. \nBoth files are in the same source directory as in the screenshot. \n\nI didnt add any exclude pattern. \nFile path is also same only pattern is different.\n"
},
{
"author": "naghma_parween",
"body": "![artifact.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/313039i8BE111B18FC308FC/image-size/large?v=v2&px=999 \"artifact.PNG\")![filepath.png](https://community.atlassian.com/t5/image/serverpage/image-id/313041iCF94BE702A2CE693/image-size/large?v=v2&px=999 \"filepath.png\")![screenshot.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/313040i496F6476B482509E/image-size/large?v=v2&px=999 \"screenshot.PNG\")\n"
},
{
"author": "naghma_parween",
"body": "With xcresult.zip pattern.\n\n![artifacts.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/313042iC5EE0D90EA272927/image-size/large?v=v2&px=999 \"artifacts.PNG\")![filepath.png](https://community.atlassian.com/t5/image/serverpage/image-id/313043i8175D5E997F1D6F6/image-size/large?v=v2&px=999 \"filepath.png\")\n"
},
{
"author": "Shashank Kumar",
"body": "Thanks for all the details.\n\nI'll try to test few things today and confirm the behaviour in my local machine and will keep you posted on the thread here.\n\nRegards,\n\nShashank Kumar\n"
},
{
"author": "Shashank Kumar",
"body": "Hi Naghma,\n\nI am not able to replicate this on 9.4.1, probably something specific to your Instance, this might need some detailed investigation, If you have a valid SEN you can raise a support request with Atlassian support.\n\nOr I would let other community members opine their thoughts on this.\n\nRegards,\n\nShashank Kumar\n"
},
{
"author": "naghma_parween",
"body": "Hi Shashank, \n\nI got to know what the problem was. '.xcresult' file is of type result bundle. Basically it;s treated as a folder structure. So I was not able to pick it up as file. I changed the file pattern to \\*\\*/\\*.\\* and it was picked up along with other files. \n\n![artifact-test.png](https://community.atlassian.com/t5/image/serverpage/image-id/313574i2E6EE012990FA178/image-size/large?v=v2&px=999 \"artifact-test.png\")\n"
},
{
"author": "Shashank Kumar",
"body": "Thanks for letting us know!\n"
}
]
}
]
| https://community.atlassian.com/t5/Bamboo-questions/Is-xcresult-file-type-not-supported-as-bamboo-artifact/qaq-p/2641585 | [
"artefact",
"build",
"fastlane",
"ios"
]
|
{
"author": "Gowse shaik",
"title": "Bamboo 6.8 version installation with MS SQL server getting Cannot insert duplicate key in object 'db",
"body": "Bamboo 6.8 version installation with MS SQL server getting \"Cannot insert duplicate key in object 'dbo.CWD_DIRECTORY'\" \nBelow is the error , i got. appreciate your input. \n\nCaused by: java.sql.BatchUpdateException: Violation of UNIQUE KEY constraint 'uk_dir_l_name'. Cannot insert duplicate key in object 'dbo.CWD_DIRECTORY'. The duplicate key value is (bamboo internal directory). \nat com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeBatch(SQLServerPreparedStatement.java:1824) \nat com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:2544) \nat org.hibernate.engine.jdbc.batch.internal.BatchingBatch.performExecution(BatchingBatch.java:118) \n... 209 more \n2024-03-05 11:00:43,454 ERROR \\[http-nio-8085-exec-18\\] \\[FiveOhOh\\] 500 Exception was thrown. \norg.springframework.dao.DataIntegrityViolationException: could not execute batch; SQL \\[insert into CWD_DIRECTORY (DIRECTORY_NAME, LOWER_DIRECTORY_NAME, CREATED_DATE, UPDATED_DATE, ACTIVE, DESCRIPTION, IMPL_CLASS, LOWER_IMPL_CLASS, DIRECTORY_TYPE, ID) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\\]; constraint \\[null\\]; nested exception is org.hibernate.exception.ConstraintViolationException: could not execute batch \nat org.springframework.orm.hibernate5.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:247) \n\n<br />\n\n<br />\n\nCaused by: org.hibernate.exception.ConstraintViolationException: could not execute batch \nat org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:112) \nat org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:42) \nat org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:113) \n\n<br />\n\n<br />\n\nCaused by: java.sql.BatchUpdateException: Violation of UNIQUE KEY constraint 'uk_dir_l_name'. Cannot insert duplicate key in object 'dbo.CWD_DIRECTORY'. The duplicate key value is (bamboo internal directory). \nat com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeBatch(SQLServerPreparedStatement.java:1824) \nat com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:2544) \nat org.hibernate.engine.jdbc.batch.internal.BatchingBatch.performExecution(BatchingBatch.java:118) \n\n<br />\n\n<br />\n\n<br />\n"
} | [
{
"author": "Jyothi Charupalli",
"body": "Hi Gowse,\n\nWelcome to the Atlassian Community!\n\nDuring Bamboo setup double clicking on some of the steps when creating an admin user causes these kinds of errors and issues.\n\nFrom the provided logs we can see the errors are caused by primary key violation \"uk_dir_l_name\" which is caused by a duplicate entry in the database table \"CWD_DIRECTORY\".\n\nThis is explained in this BUG report: <https://jira.atlassian.com/browse/BAM-21032>. This BUG got fixed in Bamboo 8.1.1 version. We suggest you install the latest versions of Bamboo to not get affected by this BUG.\n\nIn case you want to install Bamboo 6.8 Version(EOL version) only for any upgrade of Bamboo or cloning the instance, the workaround would be to re-create your environment with the new $BAMBOO_HOME directory and new database.\n\nRegards,\n\nJyothi Charupalli\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Bamboo-questions/Bamboo-6-8-version-installation-with-MS-SQL-server-getting/qaq-p/2629413 | [
"ms-sql"
]
|
{
"author": "Devendar Gangapuram",
"title": "BAMBOO task to use Token based authentication in the CURL script to create JIRA ticket",
"body": "Hi Team,\n\nI want to create JIRA ticket using the below **CRL** script by executing form Bamboo task. When we using basic authentication credentials in curl like below, it is creating JIRA ticket fine.\n\n**Basic Authentication script, this is working fine.**\n\ncurl -D- -u abcd:test1234 -X POST --data \"{\\\\\"fields\\\\\":{\\\\\"project\\\\\": {\\\\\"key\\\\\": \\\\\"HELLOWS\\\\\" }, \\\\\"summary\\\\\": \\\\\"${bamboo.planName} - ${bamboo.buildNumber}\\\\\", \\\\\"customfield_11601\\\\\": \\\\\"${bamboo.planKey}-${bamboo.buildNumber}\\\\\", \\\\\"customfield_11600\\\\\": \\\\\"${bamboo.proj.pom.releaseVersion}\\\\n\\\\\", \\\\\"description\\\\\": \\\\\"Link to the build:\\\\n${bamboo.resultsUrl}\\\\n Link to UAT Deployment logs:\\\\n <https://bamboo-uat.appD.appZ.com/browse/RT-HELLOWSUAT/deployments> \\\\n Link to PROD Deployment logs:\\\\n <https://bamboo-uat.appD.appZ.com/browse/RT-HELLOWSPROD/deployments> \\\\n \\\\\",\\\\\"issuetype\\\\\": {\\\\\"name\\\\\": \\\\\"Task\\\\\"}}}\" -H \"Content-Type: application/json\" -k <https://jira-uat.appD.appZ.com/rest/api/2/issue/>\n\n**Output**: I can see JIRA new ticket created.\n\n**But , when I am trying to use Token based authentication in the CURL script, it gives bad substitution error and it is taking other JIRA project key(AUTJT), where I actually trying to create for the JIRA project key \"HELLOWS\".**\n\n**CURL Script is:-**\n\ncurl -D- -u \"Authorization: Bearer +ZZx2sJona6Cqeo37KjfvRv\" -X POST --data \"{\\\\\"fields\\\\\":{\\\\\"project\\\\\": {\\\\\"key\\\\\": \\\\\"HELLOWS\\\\\" }, \\\\\"summary\\\\\": \\\\\"${bamboo.planName} - ${bamboo.buildNumber}\\\\\", \\\\\"customfield_11601\\\\\": \\\\\"${bamboo.planKey}-${bamboo.buildNumber}\\\\\", \\\\\"customfield_11600\\\\\": \\\\\"${bamboo.proj.pom.releaseVersion}\\\\n\\\\\", \\\\\"description\\\\\": \\\\\"Link to the build:\\\\n${bamboo.resultsUrl}\\\\n Link to UAT Deployment logs:\\\\n \n<https://bamboo-uat.appD.appZ.com/browse/RT-HELLOWSUAT/deployments> \n\\\\n Link to PROD Deployment logs:\\\\n \n<https://bamboo-uat.appD.appZ.com/browse/RT-HELLOWSPROD/deployments> \n\\\\n \\\\\",\\\\\"issuetype\\\\\": {\\\\\"name\\\\\": \\\\\"Task\\\\\"}}}\" -H \"Content-Type: application/json\" -k \n<https://jira-uat.appD.appZ.com/rest/api/2/issue/>\n\n<br />\n\n**output:** \n/bamboo/application-data/temp/RT-AUTJT-JOB1-35-ScriptBuildTask-6485507220746562543.sh: line 1: {\"fields\":{\"project\": {\"key\": \"HELLOWS\" }, \"summary\": \"Retail Transformation - AutoJIRATicketPlan - 35\", \"customfield_11601\": \"RT-AUTJT-35\", \"customfield_11600\": \"${bamboo.proj.pom.releaseVersion}\\\\n\", \"description\": \"Link to the build:\\\\n \n[https://bamboo-uat.appD.appZ.com/browse/RT-AUTJT-JOB1-35\\\\](https://bamboo-uat.appD.appZ.com/browse/RT-AUTJT-JOB1-35\\)n \nLink to UAT Deployment logs:\\\\n \n<https://bamboo-uat.appD.appZ.com/browse/RT-HELLOWSUAT/deployments> \n\\\\n Link to PROD Deployment logs:\\\\n \n<https://bamboo-uat.appD.appZ.com/browse/RT-HELLOWSPROD/deployments> \n\\\\n \",\"issuetype\": {\"name\": \"Task\"}}}: **bad substitution**\n\nNow, please help me, how to create the JIRA ticket using the token based authentication in the CURL, and also, form where it is referring the other project key?\n\nThanks,\n\nDev G\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello Dev G,\n\nWelcome to Atlassian community\n\nI think you are using **-u**for both user_id password \\& PAT token based authentication, the API will not differ based on what authentication type you are choosing.\n\nFor using PAT Tokens you can use an example like this, refer [PAT Tokens](https://confluence.atlassian.com/bamboo/personal-access-tokens-976779873.html)\n\n curl -H \"Authorization: Bearer NDc4NDkyNDg3ODE3OstHYSeYC1UgXqRacSqvUbookcZk\" http://localhost:8085/bamboo/rest/api/latest/plan/PROJ-PLAN \n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Bamboo-questions/BAMBOO-task-to-use-Token-based-authentication-in-the-CURL-script/qaq-p/2624145 | [
"api",
"curl",
"jira-soft",
"task",
"ticket"
]
|
{
"author": "swati.awate",
"title": "Unable to publish artifact Non required job artifact Http Compression Off",
"body": "Hi.\n\nI had started my bamboo server on remote agent. Installed my plugin build and performed scan which generates pdf report and it should be visible on artifact. But it is giving me error message as:\n\nUnable to publish artifact Non required job artifact Http Compression Off : \\[PDF Report\\], patterns:\n\nCan you please help me with this\n"
} | [
{
"author": "Shashank Kumar",
"body": ".\n",
"comments": null
},
{
"author": "Shashank Kumar",
"body": "Hello Swati,\n\nWelcome to Atlassian community.\n\nThe above error usually means that there are some mismatch with the way the artifact definition for the Job and the actual artifact which has been generated.\n\nThis can either be Artifact pattern, location where Bamboo is expecting it etc.\n\nCan you go to the Job where you have defined this artifact and check it's definition and see if everything is correct, refer the below screen to check the parameters.\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/309454i8A5D7A2EA28148FE/image-size/large?v=v2&px=999 \"image.png\") \n\nBTW which plugin you are using to Build ?\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": [
{
"author": "swati.awate",
"body": "![Screenshot 2024-02-29 214928.png](https://community.atlassian.com/t5/image/serverpage/image-id/309475iA9066214774EEACE/image-size/large?v=v2&px=999 \"Screenshot 2024-02-29 214928.png\")![Screenshot 2024-02-29 215106.png](https://community.atlassian.com/t5/image/serverpage/image-id/309477iE078B233FB0FA228/image-size/large?v=v2&px=999 \"Screenshot 2024-02-29 215106.png\")As mentioned I made these settings, I did not get any error in log but at artifact it is not showing any pdf. Can you send entire setting to be done related to artifact.\n"
},
{
"author": "Shashank Kumar",
"body": "Hey Swati,\n\nYou've not specified a location within your Build directory where your Artifact would be located, this is a relative path inside your Build directory, this needs to be mentioned under location field in the above attachment.\n\nIf you open your Build directory for the build which failed, where are you able to see the PDF files? can you paste the location here?\n\nRead [Bamboo artifact definition syntax examples](https://confluence.atlassian.com/bamkb/bamboo-artifact-definition-syntax-examples-815581285.html) for more details.\n\nRegards,\n\nShashank Kumar\n"
},
{
"author": "swati.awate",
"body": "Hi Shashank,\n\nThanks for your input, it worked. But issue is at particular location there are multiple pdf getting generated with timestamp pattern. I want it should get latest generated pdf and download it on artifact.\n"
},
{
"author": "swati.awate",
"body": "And 1 more doubt I had this Edit Artifact Definition we have to configure for each plan. Is there any global setting for this? So that all the projects will have same global setting for plan\n"
},
{
"author": "Shashank Kumar",
"body": "Hi Swati,\n\nFor your first query as far as I am aware you can't define artifacts to be generated with the modified time, currently your definition says **\\*.pdf** so Bamboo will pick all the files with this pattern and generate the artifact. If you want to filter it then you'll need to either give a specific file name or a more filtered location.\n\nProbably you can look to enable **Job -\\> other -\\> \"Clean working directory after each build\"**option so that older artifacts ( older .pdf files ) are cleaned up and only the latest files with .pdf extension are present.\n\nFor the second query artifact definition is specific to each Job for each Plan, there is no Global setting to define it at bulk.\n\nRegards,\n\nShashank Kumar\n"
},
{
"author": "swati.awate",
"body": "Hi Shashank. After enable checkbox \"**Clean working directory after each build\"** I am able to see single file in my Artifact section. But where PDFs are available that it works even after the clean up of build directory?\n"
},
{
"author": "Shashank Kumar",
"body": "Hello Swati,\n\nThese PDF files will move to the Artifact location which you have specified on your bamboo.cfg.xml file, probably on your Bamboo server.\n\n```\n<property name=\"bamboo.artifacts.directory\">${bambooSharedHome}/artifacts</property>\n```\n\nThis page <https://confluence.atlassian.com/bamkb/artifacts-in-bamboo-server-829052138.html> can help you locate that on Bamboo server.\n\nRegards,\n\nShashank Kumar\n"
},
{
"author": "swati.awate",
"body": "Hi Shashank.\n\nI did similar setup on Data center but on artifact section I am able to download PDF where in on Summary Section PDF is not visible.\n\nURL of Artifact Section: \"http://\\*\\*\\*/bamboo/browse/PDFGEN-TES2-9/artifact/JOB1/PDFReport/\\*\\*\\*.pdf\"\n\nURL of Summary Section: \"http://\\*\\*\\*/browse/PDFGEN-TES2-9/artifact/JOB1/PDFReport/\\*\\*\\*.pdf\"\n"
},
{
"author": "Shashank Kumar",
"body": "Hello Swati,\n\nArtifact will only be displayed in the Summary section if while defining the artifact you have selected it to be **shared**. See below\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/310518iCFCA6A2C26531C3F/image-size/large?v=v2&px=999 \"image.png\")\n"
},
{
"author": "swati.awate",
"body": "It worked. But without checking shared checkbox it had worked on Bamboo server+ remote agent. I was able to generate PDF report on both summary and Artifact section. Why similar configurations did not work for Data center? Why it worked after we checked Shared checkbox?\n"
}
]
},
{
"author": "swati.awate",
"body": "hi [@Shashank Kumar](/t5/user/viewprofilepage/user-id/4693340) ,Getting below error while Generate PDF checkbox is unchecked. How to fix this issue\n\n```\nsimple 26-Mar-2024 06:18:43 Publishing an artifact: PDFReporterror 26-Mar-2024 06:18:43 Unable to publish artifact [PDFReport]: the source directory /***/build-dir/PDFGEN-TES2-JOB1/*** does not exist.simple 26-Mar-2024 06:18:43 The artifact hasn't been successfully published after 329.1 ?ssimple 26-Mar-2024 06:18:43 Successfully removed working directory at '/***/build-dir/PDFGEN-TES2-JOB1'simple 26-Mar-2024 06:18:43 Finalising the build...simple 26-Mar-2024 06:18:43 Stopping timer.simple 26-Mar-2024 06:18:43 Build PDFGEN-TES2-JOB1-20 completed.\n```\n",
"comments": null
},
{
"author": "swati.awate",
"body": "Hi [@Shashank Kumar](/t5/user/viewprofilepage/user-id/4693340) ,\n\nCan you please check this issue I am facing.\n\nlink : [Unable to generate PDF in Summary Section (atlassian.com)](https://community.atlassian.com/t5/Bamboo-questions/Unable-to-generate-PDF-in-Summary-Section/qaq-p/2650919#M33691)\n",
"comments": [
{
"author": "Shashank Kumar",
"body": "Hello Swati,\n\nThanks for posting the question on community, I am not available currently to check the new issue, I would expect some other community members to reply to the issue soon.\n\nIf this is urgent for you and if you have a valid SEN please raise a support request with Atlassian.\n\nRegards,\n\nShashank Kumar\n"
}
]
},
{
"author": "swati.awate",
"body": "Continuing above issue on community:\n\n[Unable to generate PDF in Summary Section (atlassian.com)](https://community.atlassian.com/t5/Bamboo-questions/Unable-to-generate-PDF-in-Summary-Section/qaq-p/2650919#M33691)\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Bamboo-questions/Unable-to-publish-artifact-Non-required-job-artifact-Http/qaq-p/2625203 | null |
{
"author": "Ahmet Melih Kara?a?l?",
"title": "How to add H2 Database to Bamboo on Docker",
"body": "I set up a Bamboo on Docker. After Bamboo service started, I chose the H2 database, and encountered the following error.\n\n![Screenshot 2024-02-28 at 14.11.03.png](/t5/image/serverpage/image-id/309173iA9C10FD7A7EB32A5/image-dimensions/419x115?v=v2 \"Screenshot 2024-02-28 at 14.11.03.png\")\n\nAfter adding the h2.x.x.xxx.jar file to the server in \\<BAMBOO_INSTALL_DIR\\>/lib and restarting, the jar file gets deleted.\n\nHow can I connect the H2 database to Bamboo on Docker?\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello Ahmet,\n\nWelcome to Atlassian community.\n\nIn recent version of Bamboo H2 Jar has been removed by default as it poses security vulnerability, you can try the below steps to copy the jar if you wish.\n\nBelow is an example to copy mysql-connector-java.x.y.z.jar to the lib directory here bamboo is the name of the container.\n\n```\ndocker cp mysql-connector-java.x.y.z.jar bambooo:/opt/atlassian/bamboo/libdocker restart bamboo\n```\n\nCan you try the above steps and let me know if it works.\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": null
}
]
| https://community.atlassian.com/t5/Bamboo-questions/How-to-add-H2-Database-to-Bamboo-on-Docker/qaq-p/2623647 | null |
{
"author": "Andy Huang",
"title": "bamboo showing no webpage was found",
"body": "after a reboot of bamboo virtual machine, when accessing bamboo portal using browser showing \"no webpage was found\". both bamboo \\& postgres service seems to be running:\n\nbamboo 6541 1 6 15:16 ? 00:00:37 /usr/bin/java -Djava.util.logging.config.file=/opt/atlassian/bambo /conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -XX:MaxPermSize=256m -Xms256m -Xmx384m -Djava.endorsed.dirs=/opt/atlassian/bamboo/endorsed -classpath /opt/atlassian/bamboo/bin/bootstrap.jar:/opt/atlassian/bamboo/bin/tomcat-juli.jar -Dcatalina.base=/opt/atlassian/bamboo -Dcatalina.home=/opt/atlassian/bamboo -Djava.io.tmpdir=/opt/atlassian/bamboo/temp org.apache.catalina.startup.Bootstrap start\n\npostgres 6162 1 0 15:16 ? 00:00:00 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432 \npostgres 6221 6162 0 15:16 ? 00:00:00 postgres: logger process \npostgres 6254 6162 0 15:16 ? 00:00:00 postgres: checkpointer process \npostgres 6256 6162 0 15:16 ? 00:00:00 postgres: writer process \npostgres 6257 6162 0 15:16 ? 00:00:00 postgres: wal writer process \npostgres 6258 6162 0 15:16 ? 00:00:00 postgres: autovacuum launcher process \npostgres 6259 6162 0 15:16 ? 00:00:00 postgres: stats collector process \nroot 7175 6647 0 15:27 pts/0 00:00:00 grep --color=auto postgre\n\nwhen it was working can see some following processes, but don't seem to find them anymore:\n\npostgres 14535 6157 0 11:26 ? 00:00:00 postgres: bamboo bamboo 127.0.0.1(47356) idle \npostgres 14613 6157 0 11:27 ? 00:00:00 postgres: bamboo bamboo 127.0.0.1(47360) idle \npostgres 14614 6157 0 11:27 ? 00:00:00 postgres: bamboo bamboo 127.0.0.1(47361) idle\n\ndid anyone have the same issue before? not sure what caused this, can anyone help, thanks.\n"
} | [
{
"author": "Anik Sengupta",
"body": "Hi Andy,\n\nWelcome to Atlassian community\n\nThere can be multiple reasons for this error, can you try to replicate this error and during the same time check **\\<bamboo-home\\>logs\\>atlassian-bamboo.log** file to see what exception is being throw?\n\nBased on the exception we can try to understand the problem and the solution\n\nQuick note did you try to restart the DB service and check if the error goes.\n\nRegards,\n\nAnik Sengupta\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": [
{
"author": "Andy Huang",
"body": "Hi Anik, thanks for your response. I checked the log yesterday and following the following, seems related to ActiveMQ, but don't seem to find what caused this. I did reboot the whole vm which should also reboot both db \\& bamboo, but no luck.\n\nat com.atlassian.bamboo.plugins.git.NativeGitOperationHelper$1.call(NativeGitOperationHelper.java:488) \nat com.atlassian.bamboo.plugins.git.NativeGitOperationHelper$1.call(NativeGitOperationHelper.java:479) \nat com.atlassian.bamboo.util.CallableResultCache$1.load(CallableResultCache.java:52) \nat com.atlassian.bamboo.util.CallableResultCache$1.load(CallableResultCache.java:48) \nat com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) \nat com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350) \nat com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) \nat com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) \nat com.google.common.cache.LocalCache.get(LocalCache.java:3965) \nat com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3969) \nat com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4829) \nat com.atlassian.bamboo.collections.AlwaysInvalidatingCacheDecorator.get(AlwaysInvalidatingCacheDecorator.java:81) \nat com.atlassian.bamboo.collections.AlwaysInvalidatingCacheDecorator.getUnchecked(AlwaysInvalidatingCacheDecorator.java:135) \n... 30 more \n2024-02-28 14:22:45,332 INFO \\[10-BAM::Default Agent::Agent:pool-25-thread-1\\] \\[BuildAgentControllerImpl\\] Agent 131073 checking build queue for executables... \n2024-02-28 14:23:06,044 INFO \\[ActiveMQ ShutdownHook\\] \\[BrokerService\\] Apache ActiveMQ 5.9.0 (bamboo, ID:bamboo.dominionvoting.com-42954-1701718328709-0:1) is shutting down \n2024-02-28 14:23:06,177 INFO \\[localhost-startStop-2\\] \\[Dispatchers\\] Dispatcher org.apache.struts2.dispatcher.Dispatcher destroyed \n2024-02-28 14:23:06,198 INFO \\[localhost-startStop-2\\] \\[Dispatchers\\] Dispatcher org.apache.struts2.dispatcher.Dispatcher destroyed \n2024-02-28 14:23:06,219 INFO \\[localhost-startStop-2\\] \\[QuartzScheduler\\] Scheduler scheduler_$_NON_CLUSTERED paused. \n2024-02-28 14:23:07,004 INFO \\[localhost-startStop-2\\] \\[SVNClientManagerFactory\\] Destroying SVNClientManagerFactories... \n2024-02-28 14:23:07,792 INFO \\[ActiveMQ ShutdownHook\\] \\[TransportConnector\\] Connector tcp://bamboo.dominionvoting.com:54663?wireFormat.maxInactivityDuration=300000 stopped \n2024-02-28 14:23:07,799 INFO \\[localhost-startStop-2\\] \\[PooledConnection\\] failed to delete Temporary Queue \"temp-queue://ID:bamboo.dominionvoting.com-42954-1701718328709-3:1:6\" on closing pooled connection: peer (vm://bamboo#1) stopped. \n2024-02-28 14:23:07,799 WARN \\[localhost-startStop-2\\] \\[DisposableBeanAdapter\\] Invocation of destroy method failed on bean with name 'bandanaManagerService': javax.jms.JMSException: Peer (vm://bamboo#1) disposed. \n2024-02-28 14:23:07,799 WARN \\[localhost-startStop-2\\] \\[DisposableBeanAdapter\\] Invocation of destroy method failed on bean with name 'capabilityManagerService': javax.jms.JMSException: Peer (vm://bamboo#1) disposed. \n2024-02-28 14:23:07,799 WARN \\[localhost-startStop-2\\] \\[DisposableBeanAdapter\\] Invocation of destroy method failed on bean with name 'agentQueueAccessorService': javax.jms.JMSException: Peer (vm://bamboo#1) disposed. \n2024-02-28 14:23:07,799 WARN \\[localhost-startStop-2\\] \\[DisposableBeanAdapter\\] Invocation of destroy method failed on bean with name 'remoteAgentAdministrationConfigurationAccessorService': javax.jms.JMSException: Peer (vm://bamboo#1) disposed. \n2024-02-28 14:23:07,799 WARN \\[localhost-startStop-2\\] \\[DisposableBeanAdapter\\] Invocation of destroy method failed on bean with name 'remoteAgentManagerService': javax.jms.JMSException: Peer (vm://bamboo#1) disposed. \n2024-02-28 14:23:07,814 INFO \\[ActiveMQ ShutdownHook\\] \\[TransportConnector\\] Connector vm://bamboo stopped \n2024-02-28 14:23:07,816 INFO \\[ActiveMQ Connection Executor: vm://bamboo#0\\] \\[PooledConnectionFactory\\] Expiring connection ActiveMQConnection {id=ID:bamboo.dominionvoting.com-42954-1701718328709-3:1,clientId=ID:bamboo.dominionvoting.com-42954-1701718328709-2:1,started=false} on IOException: org.apache.activemq.transport.TransportDisposedIOException: peer (vm://bamboo#1) stopped. \n2024-02-28 14:23:07,816 INFO \\[localhost-startStop-2\\] \\[ShutdownEnforcer\\] Container being shut down: starting last-resort termination thread. \n2024-02-28 14:23:07,819 INFO \\[localhost-startStop-2\\] \\[AgentManagerImpl\\] Stopping all local agents... \n2024-02-28 14:23:07,819 WARN \\[10-BAM::Default Agent::Agent:pool-25-thread-1\\] \\[BuildAgentControllerImpl\\] Building interrupted. Stopping agent 'Default Agent'... \n2024-02-28 14:23:07,819 INFO \\[10-BAM::Default Agent::Agent:pool-25-thread-1\\] \\[DefaultBuildAgent\\] Changing context: null -\\> null on Default Agent/23211f71 \n2024-02-28 14:23:07,819 INFO \\[10-BAM::Default Agent::Agent:pool-25-thread-1\\] \\[DefaultBuildAgent\\] Build agent 'Default Agent' stopped. \n2024-02-28 14:23:07,823 INFO \\[ActiveMQ ShutdownHook\\] \\[PListStoreImpl\\] PListStore:\\[/home/bamboo/bamboo-home/jms-store/bamboo/tmp_storage\\] stopped \n2024-02-28 14:23:07,824 INFO \\[ActiveMQ ShutdownHook\\] \\[KahaDBStore\\] Stopping async queue tasks \n2024-02-28 14:23:07,824 INFO \\[ActiveMQ ShutdownHook\\] \\[KahaDBStore\\] Stopping async topic tasks \n2024-02-28 14:23:07,824 INFO \\[ActiveMQ ShutdownHook\\] \\[KahaDBStore\\] Stopped KahaDB \n2024-02-28 14:23:07,831 INFO \\[localhost-startStop-2\\] \\[QuartzScheduler\\] Scheduler scheduler_$_NON_CLUSTERED shutting down. \n2024-02-28 14:23:07,832 INFO \\[localhost-startStop-2\\] \\[QuartzScheduler\\] Scheduler scheduler_$_NON_CLUSTERED paused. \n2024-02-28 14:23:07,837 INFO \\[localhost-startStop-2\\] \\[QuartzScheduler\\] Scheduler scheduler_$_NON_CLUSTERED shutdown complete. \n2024-02-28 14:23:07,840 INFO \\[localhost-startStop-2\\] \\[ConfigurableLocalSessionFactoryBean\\] Closing Hibernate SessionFactory \n2024-02-28 14:23:07,864 INFO \\[localhost-startStop-2\\] \\[BambooPluginManager\\] Plugin state will no longer be persisted.\n"
},
{
"author": "Anik Sengupta",
"body": "Hi Andy,\n\nI see that the error string itself has been truncated. Can you send us the complete error snippet.\n\nAlso the below logs which you see are after Bamboo is shutting down\n\n*2024-02-28 14:22:45,332 INFO \\[10-BAM::Default Agent::Agent:pool-25-thread-1\\] \\[BuildAgentControllerImpl\\] Agent 131073 checking build queue for executables...* \n*2024-02-28 14:23:06,044 INFO \\[ActiveMQ ShutdownHook\\] \\[BrokerService\\] Apache ActiveMQ 5.9.0 (bamboo, ID:bamboo.dominionvoting.com-42954-1701718328709-0:1) is shutting down*\n\nRegards,\n\nAnik Sengupta\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n"
},
{
"author": "Andy Huang",
"body": "I have downloaded the whole atlassian-bamboo.log file, and zipped to 238KB, anywhere I can upload it? Thanks.\n"
},
{
"author": "Anik Sengupta",
"body": "Instead of uploading the complete file, can you paste the complete error snippet\n"
},
{
"author": "Andy Huang",
"body": "Hi Anik, unfortunately I don't know what specific I have to look for that's why I am trying to upload the whole log file. If that can't be done, any key word I should use to search for in the log file? Thanks.\n"
},
{
"author": "Andy Huang",
"body": "Hi Anik, can you advise where the truncated error is in the log file, I can try to find the complete error snippet, thanks.\n"
},
{
"author": "Jyothi Charupalli",
"body": "Hi Andy,\n\nCan you please provide the error screenshot you are getting while accessing Bamboo UI?\n\nDo you have any proxy setup before Bamboo server? If yes, could you please check if it is updated in \\<Bamboo-Install-Directory\\>/conf/server.xml.\n\nDo you see any errors in the \\<Bamboo-Install-Directory\\>/logs/catalina.out file when accessing the Bamboo UI?\n\nIs your Bamboo server reachable from the internet, do you have any DNS configuration for Bamboo server before the virtual machine reboot in the/etc/hosts file?\n\nWe might need a complete Bamboo support zip which will help us to check the complete server logs. If in case we are not able to get any clue from the above mentioned details, we suggest you raise a support ticket to our Bamboo support team to further investigate the issue.\n\nRegards,\n\nJyothi Charupalli\n"
},
{
"author": "Andy Huang",
"body": "Hi Jyothi, please see attached screenshot. I don't see proxy config in \\<Bamboo-Install-Directory\\>/conf/server.xml. I don't see any lines added to \\<Bamboo-Install-Directory\\>/logs/catalina.out file when access bamboo UI. The bamboo server isn't reachable from the internet. Currently there are only 2 localhost lines, there is no DNS config in /etc/hosts file. How do I generate a complete bamboo support zip? Thanks.![screenshot.png](https://community.atlassian.com/t5/image/serverpage/image-id/310307iA92CEBA1E0368154/image-size/large?v=v2&px=999 \"screenshot.png\")\n"
},
{
"author": "Jyothi Charupalli",
"body": "Hi Andy,\n\nThanks for the response.\n\nTo check the issue further, you can do the following and provide the output:\n\n1. Test connection to Bamboo: telnet bamboo.dominionvoting.com 8085\n\n2. ping bamboo.dominionvoting.com\n\n3. Check the Java path defined on Bamboo server: echo $JAVA_HOME\n\nAs Bamboo is down now you can't create a support zip currently but for your reference in future on how to [create a support zip](https://confluence.atlassian.com/support/create-a-support-zip-790796819.html).\n\nTo create a support request to Atlassian Support:<https://support.atlassian.com/contact/#/>\n\nBest Regards,\n\nJyothi\n"
},
{
"author": "Andy Huang",
"body": "Hi Jyothi,\n\nAppreciate your help. I test telnet, ping both work. output of echo $JAVA_HOME is /usr/java/latest. Is self-hosted bamboo support still available? I thought it's ended since Feb. 15, 2024?\n"
},
{
"author": "Jyothi Charupalli",
"body": "Hi Andy,\n\nYes, for Bamboo server products, support ended on FEB 15th 2024. In order to get assistance from the Atlassian support team, you need to get a Datacenter license. Please refer <https://www.atlassian.com/software/bamboo/download>.\n\n```\necho $JAVA_HOME is /usr/java/latest \n```\n\nCan you please check if this is the correct Java home path pointing to your Java JDK path?\n\nPlease confirm your Bamboo version and Java version on the server.\n\nRegards,\n\nJyothi\n"
},
{
"author": "Andy Huang",
"body": "Hi Jyothi,\n\nFollowing is my findings:\n\n\\*. output of echo $JAVA_HOME is /usr/java/latest\n\n\\*. bamboo install folder: /opt/atlassian/atlassian-bamboo-5.7.2/, assume bamboo version is 5.7.2\n\n\\*. java version \"1.8.0_191\" \nJava(TM) SE Runtime Environment (build 1.8.0_191-b12) \nJava HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode)\n"
}
]
}
]
| https://community.atlassian.com/t5/Bamboo-questions/bamboo-showing-no-webpage-was-found/qaq-p/2624500 | null |
{
"author": "Arthur Parisis",
"title": "I need to upgrade to bamboo v8 daatacenter. What is the minimum windows server OS compatible?",
"body": "I need to upgrade to bamboo v8 daatacenter. What is the minimum windows server OS compatible?\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello Arthur,\n\nWelcome to Atlassian community.\n\nAs per <https://confluence.atlassian.com/bamboo/supported-platforms-289276764.html> there is no specific version of Windows mentioned.\n\nYou can give a try on any specific Windows OS and see if it works. I've seen people install Bamboo 8 on Windows server 2019 and it has worked fine.\n\nRegards,\n\nShashank kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": [
{
"author": "Ayrijit Swain",
"body": "Hello [@Arthur Parisis](/t5/user/viewprofilepage/user-id/5439439) ,\n\nTo add to above, although Bamboo does not have any limitations with respect to the Windows OS version, there are limitations on supported Java version, Git versions and Database types and version which are compatible with Bamboo.\n\nMake sure the OS version you select is compatible with these software requirements.\n\nAdditionally you can read about **Bamboo Best practises - System Requirements** in the knowledge article: <https://confluence.atlassian.com/bamboo0802/bamboo-best-practice-system-requirements-1103433708.html>\n\nRegards,\n\nAyrijit\n"
}
]
}
]
| https://community.atlassian.com/t5/Bamboo-questions/I-need-to-upgrade-to-bamboo-v8-daatacenter-What-is-the-minimum/qaq-p/2621953 | null |
{
"author": "Devendar Gangapuram",
"title": "Best way to transfer projects and plans to another bamboo instance.",
"body": "HI Team,\n\nWe have **on-prem** Bamboo server installed and it has a project with**200+** plans(**Build+Deploy** ). Now we have to move this entire data from this Bamboo server (**windows** )to Bamboo(**Linux**) data center instance, everything including Logs, plans, ... etc information.\n\nPlease let me know the best way to transfer our data from Windows Bamboo instance to Linux Bamboo instance .\n\nAlready referred this link l<https://confluence.atlassian.com/bamboo/exporting-data-for-backup-289277255.html> , but still need your support.\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello Dev G,\n\nWelcome to Atlassian Community.\n\nI think for your scenario you can refer this \\> <https://confluence.atlassian.com/bamboo/cloning-a-bamboo-instance-289277407.html>\n\nThere are two ways to do it, read the above page for detailed steps\n\n1) Use Import and Export\n\n2) Manually transfer the DB and Bamboo Home\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": null
},
{
"author": "Anik Sengupta",
"body": "Adding to the above, performing a full export/ import of a Bamboo instance can be very time consuming depending on the amount of artifacts and build logs you have. If your current instance has grown too large and export/ import does not work, you can still migrate your instance by using an alternative backup and restore strategy.\n\nYou can refer - <https://confluence.atlassian.com/bamkb/how-to-migrate-a-bamboo-instance-with-a-large-number-of-artifacts-and-build-logs-1093015034.html>\n",
"comments": [
{
"author": "Devendar Gangapuram",
"body": "Thank you both,\n\nNow , my requirement is, just need to migrate only 5 apps among 130, How to do it?\n\nThank you,\n\nDev G\n"
},
{
"author": "Shashank Kumar",
"body": "Hello Dev G,\n\nWhen you say Apps, do you mean External third party apps/Plugins which you have installed in your Bamboo system, please clarify.\n\nRegards,\n\nShashank Kumar\n"
},
{
"author": "Devendar Gangapuram",
"body": "Hi [@Anik Sengupta](/t5/user/viewprofilepage/user-id/4672627) ,\n\nNo, our Bamboo applications with all Build and Deployment plans with data.\n\nThank you,\n\nDev G,\n"
},
{
"author": "Shashank Kumar",
"body": "Hello Dev G,\n\nYou cannot move specific plans and Deployments easily. Import and Export will copy all the data from source to Destination.\n\nIf you want to move only specific plans and deployment, you should try Bamboo specs.<https://confluence.atlassian.com/bamboo/bamboo-specs-894743906.html>\n\nRegards,\n\nShashank Kumar\n"
}
]
}
]
| https://community.atlassian.com/t5/Bamboo-questions/Best-way-to-transfer-projects-and-plans-to-another-bamboo/qaq-p/2622166 | [
"data-center",
"migration",
"server",
"workflow"
]
|
{
"author": "Sneh Patel",
"title": "Bamboo Server Migration Approach & Issues",
"body": "**Context:**\n\nWe are currently in the process of migrating our Bamboo server hosted on CentOS 6.10 to RHEL 8.9. Our current Bamboo version is v7.0.4. We want to upgrade it to v9.2.6 or a later LTS version after migrating our server. Both the database and the app live within the same server. After migration, we will like to have a separate database server. Also, Bamboo is connected to other Atlassian products like Bitbucket and Jira (uses Jira authentication as well).\n\nWe referred to the following Atlassian documents:\n\n* [Moving Bamboo Between Machines](https://confluence.atlassian.com/bamkb/moving-bamboo-between-machines-134873224.html)\n* [Cloning Bamboo Instance](https://confluence.atlassian.com/bamboo/cloning-a-bamboo-instance-289277407.html)\n\n[Moving Bamboo Between Machines](https://confluence.atlassian.com/bamkb/moving-bamboo-between-machines-134873224.html) document recommends to use the UI utility tool to export the Bamboo instance to the new server. However, upon trying that approach, it took too long and we can't afford to have our Bamboo instance unavailable for that long.\n\n**Our Approach:**\n\nBy referring to [Cloning Bamboo Instance](https://confluence.atlassian.com/bamboo/cloning-a-bamboo-instance-289277407.html) :\n\nIn order to test the migration and upgrades, we decided to clone our existing Bamboo instance (prod) and use it as a test instance. We will then try to migrate this test instance to a different server in order to test the migration.\n\nIn order to stand the test instance in the cloned server we did the following:\n\n1. Cloned our existing Bamboo server (prod).\n2. Modified the following bamboo.cfg.xml fields within the clone:\n * \"bamboo.jms.broker.client.uri\" to point to cloned server\n * \"license.string\" to our development license \n NOTE: \n - We tried to modify the \"serverKey\" property as well but then we ran into errors with regards to decryption of certain things in the database (mismatch of encryption/decryption). \n - We didn't change the database connection string because we cloned the server so the existing bamboo database was also cloned (therefore, we still use localhost).\n3. Modified the following administration.xml fields within the clone:\n * \"myBaseUrl\" to point to cloned server\n * \"myInstanceName\" to \"Cloned Bamboo Server\"\n4. Start the service in from the installation directory: start-bamboo.sh (within the clone).\n5. Immediately configured app links to point to our test Bitbucket/Jira instances (including crowd server).\n\nOnce we successfully stand up the cloned instance (still a CentOS server), we will look to migrate it over to a new RHEL 8 server by using rsync to copy both the installation directory and the bamboo-home directory.\n\nWhen migrating the database to a database server we will use pg_dump utility to export our test Bamboo database (from the cloned server) to the new database server.\n\nWe will then start up the Bamboo service in the new RHEL 8 server. If all works at this point, then we expect to have successfully migrated the Bamboo server. We will then perform upgrades as suggested in <https://confluence.atlassian.com/bamboo/bamboo-upgrade-guide-720411366.html>.\n\n**Problems:**\n\n1. When we initially started the service in the cloned instance, Bamboo was connected to our production Bitbucket service, and so it caused some issues where PR builds were getting sent to the cloned Bamboo service (causing hanging builds). In the [Cloning Bamboo Instance](https://confluence.atlassian.com/bamboo/cloning-a-bamboo-instance-289277407.html) document, there is no note of this potential issue and how to avoid it.\n2. We were able to register a Bamboo agent to in our cloned Bamboo service. However, it seems like auto-trigger is not working. We expect it to auto-trigger upon PR creation. We checked/noted the following things:\n * We checked the health of our linked repositories by going to Admin Setting \\> System Information \\> Linked Bitbucket Server instances and it was green (connected properly).\n * We noticed that the branch was getting created within the plan however, no build is getting queued for that branch when PR was created.\n * We looked at the following thread: <https://community.atlassian.com/t5/Bamboo-questions/Bamboo-not-triggering-build-for-branches-when-code-is-pushed-to/qaq-p/1164364> but couldn't find anything in the log.\n * In atlassian-bamboo.log, we notice that there are still references to the old ssh Bitbucket url.\n * We couldn't find anything in particular within the atlassian-bamboo.log that would suggest a root cause of the issue.\n * We made sure that the files within bamboo-home directory are all owned by the root user.\n\n**Questions:**\n\n1. Is our approach correct? Or is there a better way?\n2. We are currently stuck at the part where we are trying to stand up the test Bamboo instance (after cloning existing Bamboo server) due to auto-trigger being broken. Is there a way solve this issue so that we can proceed with migrating the test instance to a new server?\n3. If possible, can someone from Atlassian provide clear steps to successfully migrating Bamboo server (like how there are clear steps when migrating [Migrating Bitbucket Server](https://confluence.atlassian.com/bitbucketserver088/migrating-bitbucket-server-to-another-server-1216582747.html?))? Kind of getting confused since we are facing issues with auto-triggering of builds (this is just 1 of the issues, there could be several other issues).\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello Sneh,\n\nWelcome to Atlassian community.\n\nLooking at your approach I don't see any problems, the only thing I don't see is that you have not modified **server.xml**file in the cloned Bamboo Instance. At minimum you'll need to change the proxy URL which should point to test instance URL if you are using any.\n\nBelow are the two documents which you can refer for cloning a Bamboo Instance.\n\n* <https://confluence.atlassian.com/bamkb/how-to-migrate-a-bamboo-instance-with-a-large-number-of-artifacts-and-build-logs-1093015034.html>\n\n* [Cloning Bamboo Instance](https://confluence.atlassian.com/bamboo/cloning-a-bamboo-instance-289277407.html)\n\nI agree that when you start the cloned instance, it triggers the build automatically as it would be connected to other apps via app links. There is a page created to explain this in detail, you can refer [How to start up Bamboo with build plans, deployment environments, branch detection and build status updates disabled](https://confluence.atlassian.com/bamkb/how-to-start-up-bamboo-with-build-plans-deployment-environments-branch-detection-and-build-status-updates-disabled-998659624.html)\n\nFor your second problem I guess when you have cloned the Bamboo Instance, the repositories are still pointing to the old bitbucket URL as now you have changed the app link to point to the new test bitbucket instance, there are two ways in which you can fix this.\n\n1. Either relink those repositories again in the cloned Bamboo Instance pointing to the repositories in the test bitbucket Instance.\n\n2. Update the URL in bulk, refer <https://jira.atlassian.com/browse/BAM-18273> this for the SQL\n\nOnce this is done I believe trigger Issue should be solved.\n\nIf you looking for someone to have a close look at this and guide you better, I believe you can raise a Support ticket with Atlassian ( If you have a valid active license ) and someone from Support team will be able to assist you further.\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n",
"comments": [
{
"author": "Sneh Patel",
"body": "Hi [@Shashank Kumar](/t5/user/viewprofilepage/user-id/4693340) thank you for your response. In response to your suggestions:\n\n1. Yes we have already tried to relink. The repositories are pointing to the new app link. I even tried to clone a plan with the repo link pointing to our test Bitbucket. However, still no luck. \n\n2. Haven't tried this. I can try it out and see if that does the trick.\n\nAlso, I don't think our server.xml uses proxy.\n\nBut nonetheless, when we do get to production migration, do you approve of the approach outlined? Instead of using the UI utility to export our Bamboo instance, can we simply use rsync on the bamboo-home directory and the installation directory? That should still successfully migrate our instance right?\n"
},
{
"author": "Shashank Kumar",
"body": "Hello Sneh,\n\nFor the Trigger problem you can try to change the URL and see if it works. Also try to add a fresh linked repository to a new test plan and see if this trigger works. This test will help you validate if the app link is working properly.\n\nYes lot of people don't use Import and Export UI utility as it takes a lot of time for import and Export and not suggest-able for large instances.\n\nThere are two basic things which you have to keep in mind\n\n1. The first step for you is to clone the current PROD instance to another server - This should be on the same version on which PROD is running ( no upgrade yet here )\n\n1.1 Clone home, install directory and copy it to new server.\n\n1.2 Also clone the DB details and update bamboo.cfg.xml file in cloned bamboo-home directory with the cloned DB details, you can use the same DB but if you want to backup or rollback you'll have problems.\n\n1.3 Here you have 3 things ( cloned home, cloned install , cloned DB )\n\n1.4 if the path of home directory is changing, make sure to update bamboo-init.properties file with new path.\n\n1.5 Now you can start the new instance, make sure the old PROD instance is not running\n\n2. After the cloned instance is up and running you can plan for upgrade to another version.\n\nThis is just a very high level summary of what you should be doing, you can refer the above attached documents for all the detailed steps including backup.\n\nAlso please test this a test environment before trying into production.\n\nRegards,\n\nShashank Kumar\n\n**\\*\\*please don't forget to Accept the answer if your query was answered\\*\\***\n"
},
{
"author": "Sneh Patel",
"body": "Thanks [@Shashank Kumar](/t5/user/viewprofilepage/user-id/4693340), I just tried to copy over the home directory and installation directory to another test server (manually), and the trigger seemed to have worked for one PR in a specific repo. However, I get the following error when I created another PR in another repo in our test Stash and thus, does not queue the build:\n\n```\n2024-02-29 15:33:56,569 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-7] [BranchCreatedEventListener] Received stash branch creation event [ base, sneh-test-pr2]\n2024-02-29 15:34:01,498 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-16] [PullRequestAwareEventListener] Received pull request opened event [ base, from: refs/heads/sneh-test-pr2, to: refs/heads/master]\n2024-02-29 15:34:01,649 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-16] [LightweightBranchCreationServiceImpl] Created branch with key CHEF-CHB127 for VCS branch VCS Branch [sneh-test-pr2]\n2024-02-29 15:34:01,882 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-7] [NativeGitOperationHelper] Could not find [sneh-test-pr2] in remote refs.\n2024-02-29 15:34:01,987 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-7] [NativeGitOperationHelper] Could not find [sneh-test-pr2] in remote refs.\njava.lang.RuntimeException: com.atlassian.bamboo.plugins.stash.repository.InvalidStashRepositoryException: Git: Cannot determine head revision of 'ssh://git@<prod_stash_url>:7999/chef/base.git' on branch 'sneh-test-pr2'. Branch has probably been removed.\nCaused by: com.atlassian.bamboo.plugins.stash.repository.InvalidStashRepositoryException: Git: Cannot determine head revision of 'ssh://<prod_stash_url>:7999/chef/base.git' on branch 'sneh-test-pr2'. Branch has probably been removed.\n2024-02-29 15:34:01,987 INFO [6-DelayedChangeDetectionThread:pool-12-thread-64] [NativeGitOperationHelper] Could not find [sneh-test-pr2] in remote refs.\ncom.atlassian.bamboo.repository.RepositoryException: com.atlassian.bamboo.plugins.stash.repository.StashRepositoryException: com.atlassian.bamboo.repository.RepositoryException: command [/usr/bin/git log -p --name-only --encoding=UTF-8 --format=[<random_chars>_BAM_hash]%H%n[<random_chars>_BAM_author_name]%aN%n[d31bfa5_BAM_author_email]%ae%n[<random_chars>_BAM_timestamp]%ct%n[<random_chars>_BAM_commit_message]%s%n%b[<random_chars>_BAM_commit_message_end]%n[<random_chars>_BAM_file_list] -1 sneh-test-pr2 ^master] failed with code 128. Working directory was [/data/bamboo-home/xml-data/build-dir/_git-repositories-cache/<some_random_hash>]., stderr:\n```\n\nI have no idea why it is still using the prod stash url when it should be using the test Stash url since our test Bamboo is connected to test Stash. Also, when I try to create a PR in test Stash (for the repo which doesn't queue the build), I do not see any reviewers automatically loaded on, whereas I see reviewers automatically loaded for the repo which has no problem queuing builds. Not sure if the issue is related. \n\nCould this be because of caching?\n"
},
{
"author": "Shashank Kumar",
"body": "Hello Sneh,\n\nThis is because you have cloned everything from PROD into a test environment.\n\nJust changing the application link will not change the URL of the already copied ( cloned ) repositories from Production.\n\nThere are two ways you can fix this.\n\n1. Delete all the Repositories ( Linked , Project and Plan Repositories ) and them again, this will make sure these repositories are pointing to the test bitbucket instance and not Prod bitbucket instance.\n\n2.You can also do this in bulk by running the SQL query which I shared earlier.\n\n3. You can try to do a fresh Reindexing which is normally recommended when a prepare a new environment after cloning, refer [Bamboo Reindexing](https://confluence.atlassian.com/bamboo/reindexing-data-289277251.html)\n\n4. For any repository if you see PROD URL in the logs you can check what URL it is pointing to by querying **VCS_LOCATION** table.\n\nRegards,\n\nShashank Kumar\n"
},
{
"author": "Sneh Patel",
"body": "Hi [@Shashank Kumar](/t5/user/viewprofilepage/user-id/4693340) thank you for your suggestions. My apologies for taking too much of your time. Based on your suggested options here are my queries:\n\n1. From options 1-3 that you laid out, we can try any ONE of them to resolve the issue right?\n2. I tried option 1 - deleted 1 linked repo (for which auto-trigger was not working) and re-added it but no luck. Is option 2 the only option? Option 2 does not seem trivial and we have a lot of repositories and also, the xml_definition field is a composition of various tags that would require parsing. This may corrupt our cloned db (for test purposes).\n3. Do you have to do option 3 regardless of whether you do 1 or 2? What exactly does re-indexing do?\n"
},
{
"author": "Shashank Kumar",
"body": "Hello Sneh,\n\nNo need for apologies as we are all here to help each other on community :)\n\n1) Coming to reindexing - This is not a 100% solution to the problem which you are seeing. Reindexing is advisable when you copy data from one DB to another and will help to eliminate any caching issue etc ( this may or may not be applicable for your problem )\n\nThe problem which you are seeing is that you have created a **Bamboo test instance** from Prod which means it contains all the Bitbucket server PROD URL for the repositories unless you fix it you'll not be able to trigger builds from Bitbucket Test Environment even if application link is pointing to Bitbucket test, this will work good if you link a new repositories.\n\nThe two options which I suggested above are the only thing I can think of.\n\nBelow are the update queries for postgres and MySQL DB as explained in <https://jira.atlassian.com/browse/BAM-18273>\n\n**PostgresDb and MySQL** : \n\n```\nupdate VCS_LOCATION as V set xml_definition_data = replace(xml_definition_data,'<old-url>','<new-url>');\n```\n\n<br />\n\n**MSSQL Server:** \n\n```\nupdate VCS_LOCATION? set XML_DEFINITION_DATA = replace( cast( XML_DEFINITION_DATA as nvarchar(max) ),'<old-url>','<new-url>'); \n```\n\n```\n?\n```\n\nYou can try this option for 1 row and see if this works and then try in bulk.\n\nRegards,\n\nShashank Kumar\n"
},
{
"author": "Sneh Patel",
"body": "I tried option 1. I removed the linked repo and re-added it again but no luck. So I guess option 2 (SQL queries) is the only option?\n"
},
{
"author": "Shashank Kumar",
"body": "In Option 1 after adding and removing the linked repository globally, you'll need to remove and re add this linked repository under the plans repository tab and resave the source code checkout task.\n\nYou'll also have to remove the git cache for this linked repository refer <https://confluence.atlassian.com/bamkb/git-cache-removal-in-bamboo-329982070.html>\n"
}
]
}
]
| https://community.atlassian.com/t5/Bamboo-questions/Bamboo-Server-Migration-Approach-amp-Issues/qaq-p/2622768 | [
"bamboo-migration"
]
|
{
"author": "Berenberg_io Team",
"title": "How to configure docker runner to authorize the different project specific private docker registry",
"body": "We've Build and Deploy user which already configured with Docker login on all of our build and deploy agents this works fine for one big private docker registory. But now we've more project specific private docker registry those have different users example (registry1=User1, registry2=User2, registry3=User3 and registry4=User4...etc) and while downloading private docker image from project specific private docker registry giving error \"unknown: Authentication is required\".\n\nHow we can configure Bamboo Job -\\> Docker to authorize with different project specific private docker registry?\n\nHere is the example of one project specific docker-staging.docker.comapny.com :\n\n![dockererror.png](/t5/image/serverpage/image-id/308655i91EE65F0829689EC/image-size/large?v=v2&px=999 \"dockererror.png\")\n"
} | [
{
"author": "Shashank Kumar",
"body": "Hello Team,\n\nI think this request is covered under this feature request I believe <https://jira.atlassian.com/browse/BAM-25259>\n\nRegards,\n\nShashank Kumar\n",
"comments": [
{
"author": "peemoeller",
"body": "Hi [@Shashank Kumar](/t5/user/viewprofilepage/user-id/4693340) , this feature would indeed help us here. But as I understand this currently is only a feature request, is there any kind of ETA available?\n"
},
{
"author": "Shashank Kumar",
"body": "Yes it's a feature request, can't say about ETA, these are prioritized based on number of votes, you can read more about it at <https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html>\n\nAs you are following it already, you'll be notified about it on email when any changes are done.\n\nRegards,\n\nShashank Kumar\n"
}
]
}
]
| https://community.atlassian.com/t5/Bamboo-questions/How-to-configure-docker-runner-to-authorize-the-different/qaq-p/2620863 | [
"authentication",
"docker",
"login",
"server"
]
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.