Datasets:

---

youngmon

/

atlassian-qna

like 2

[ { "author": "John M", "body": "Hi [@Yoav K](/t5/user/viewprofilepage/user-id/5527713) ,\n\nEach plan is on a per-page basis, so you would need to pay for each page separately. You can add multiple pages to the same account. After you add your first page you will see an option to add a new page, which will be on it's own subscription.\n\n<https://www.atlassian.com/software/statuspage/pricing>\n", "comments": [ { "author": "Yoav K", "body": "Thank you John. \nWith a free plan I can have to 2 pages live publicly, after Im trying to take the third page publicly, it says I cannot use the free plan. So I didn't understand which plan is the minimum required to have 3 pages live publicly.\n" }, { "author": "John M", "body": "Thanks for clarifying [@Yoav K](/t5/user/viewprofilepage/user-id/5527713)\n\nThe free plan is the only plan that limits the number of pages you can have on that plan: \n\n<https://support.atlassian.com/statuspage/docs/what-do-i-get-on-a-free-plan/>\n\nYou can have 2 pages on the free plan and the third page would need to be on any other plan to go live.\n" } ] } ]

[ "cloud", "statuspage-cloud" ]

[ { "author": "Mikael Sandberg", "body": "Hi [@Matt Grayford](/t5/user/viewprofilepage/user-id/4962049),\n\nWelcome to Atlassian Community!\n\nOne way of doing it would be to use an iPaaS like tray.io, workato or any of the other ones out there. They are low code/no code ways of interact with different APIs and integrations. I use tray.io for multiple things, like getting assets from Intune and Jamf into Assets, assign requests based on on-call schedule in JSM just to mention a few.\n", "comments": [ { "author": "Matt Grayford", "body": "Awesome! Thanks for the suggestions! I'll take a look at those today and see if can accomplish what I need.\n\nMatt\n" }, { "author": "Matt Grayford", "body": "Deciding to go the github route to get it situated. Thanks again!\n" } ] } ]

[ "azure-devops", "restapi", "subscribers" ]

[ { "author": "Egor", "body": "Hey Peter, \nThanks for reaching out to Atlassian Community! \n\nYes, your custom templates with translated Chinese text will display correctly on the Statuspage and in email notifications. Statuspage should render your translated content as expected. Please note that all generic messages from Statuspage are going to remain in the default language - English. \n\nIf you encounter any issues, please let us know for further assistance. \n\nBest Regards, \nEgor\n", "comments": null } ]

[ "cloud", "statuspage-cloud" ]

[ { "author": "Andy Gladstone", "body": "[@Scott Gast](/t5/user/viewprofilepage/user-id/5273333) welcome to the Atlassian Community.\n\nIf you remove SMS messaging as an option, current subscribers will not be informed of the change. It's a setting managed by you/your organization - but not something that triggers any changes or messaging to the end-user.\n\nHope this helps!\n", "comments": null } ]

[ { "author": "Egor", "body": "Hey Justin, \nThanks for reaching out to Atlassian Community! \n\nAt the moment, it is not possible to completely remove the \"Unsubscribe\" option from Statuspage notification emails. This option is automatically included in the email footer to comply with email communication best practices and regulations. \n\nQuestion 2: Modify the \"Unsubscribe\" Option:\n\nWhile you cannot remove the \"Unsubscribe\" link, you can provide additional guidance to your internal staff on what to do if they accidentally click it. \n\nBest Regards, \nEgor\n", "comments": null }, { "author": "Justin Gutierrez", "body": "Referring to the '[email protected]' emails that a customer will receive when an incident is created. Areas of concern are outlined in red.\n", "comments": null } ]

[ "notification", "subscription" ]

[ { "author": "Alan Violada", "body": "Hey Praveen, Alan from the Statuspage Support team here.\n\nStatuspage has two different APIs available - A read-only public API, and the Manage API, which has endpoints available for editing your page, creating incidents, managing subscribers, and much more.\n\nRelated documentation:\n\n[What are the different APIs under Statuspage?](https://support.atlassian.com/statuspage/docs/what-are-the-different-apis-under-statuspage/)\n\n[Manage API - Incident creation](https://developer.statuspage.io/#operation/postPagesPageIdIncidents)\n\nRegards,\n\nAlan\n", "comments": null } ]

[ "automation", "cloud", "statuspage-cloud" ]

[ { "author": "Nicolas Grossi", "body": "[@Christian Glover Wilson](/t5/user/viewprofilepage/user-id/5525338) Welcome! You might take a look at this link: <https://support.atlassian.com/statuspage/docs/enable-subscribers/>\n\nHTH\n\nNicolas\n", "comments": [ { "author": "Christian Glover Wilson", "body": "Thank you. I had consulted that, every check box is checked but there is no longer a CTA to subscribe\n" } ] } ]

[ "cloud", "statuspage-cloud" ]

[ { "author": "Chris Milton", "body": "Thanks Egor. That is unfortunate, as it would seem more logical to subscriber users to nothing by default, and then add, rather than subscribing them to everything and then taking away.\n\nThanks,\n\nChris\n", "comments": null }, { "author": "Egor", "body": "Hey Chris, \nThanks for reaching out to Atlassian Community!\n\nCurrently, Statuspage automatically subscribes new subscribers to all components by default. Unfortunately, there is no built-in option to change this behavior so that new subscribers are assigned to 0 components by default.\n\nYou would need to manually adjust their subscriptions after they are added or use the API to update their component subscriptions programmatically.\n\nIf you need further assistance, please let us know.\n\nBest Regards, \nEgor\n", "comments": null } ]

[ "cloud", "statuspage-cloud" ]

[ { "author": "Egor", "body": "Hey Haris, \n\nIn case you want to move Statuspage organization from one Atlassian site to another, then you need to contact us using the following link and we'll assist you further - <https://support.atlassian.com/contact/>\n\nBest Regards, \nEgor\n", "comments": [ { "author": "Ilze Skrulle", "body": "Hi, Egor,\n\nI cannot find the Statuspage as an option under \"Which product(s) do you want to migrate to?\\*\"\n\nWhat category should I choose for migration?\n" } ] }, { "author": "Nicolas Grossi", "body": "[@Haris Khan](/t5/user/viewprofilepage/user-id/4681698) Welcome, Actually what you mean by move status ?\n\nNicolas\n", "comments": null } ]

[ "cloud", "statuspage-cloud" ]

[ { "author": "John M", "body": "Hi [@Julia Duda](/t5/user/viewprofilepage/user-id/5522605) ,\n\nUnfortunately, we don't have a way to create parent maintenances, and as for the conversion to local timezones, we do have a feature request for this logged under STATUS-22.\n\nThis may be something you could accomplish with custom Javascript (if your plan includes custom HTML/CSS/JS) by getting the user's timezone from their browser and then converting it to local time.\n", "comments": null } ]

[ { "author": "Egor", "body": "Hey Juan, \nThanks for reaching out to Atlassian Community! \n\nPlease follow the steps described here - <https://support.atlassian.com/statuspage/docs/delete-a-page-or-organization/> \n\nIn case you're still having issues, please feel free to raise it with us.\n\nBest Regards, \nEgor\n", "comments": [ { "author": "Juan Carlos Pin", "body": "Thanks [@Egor](/t5/user/viewprofilepage/user-id/3583730) but it says\n\n![Captura de pantalla 2024-06-20 143623.png](https://community.atlassian.com/t5/image/serverpage/image-id/330878i9866240B47DAAEDB/image-size/large?v=v2&px=999 \"Captura de pantalla 2024-06-20 143623.png\")\n" } ] }, { "author": "Nicolas Grossi", "body": "[@Juan Carlos Pin](/t5/user/viewprofilepage/user-id/4667358) Did you check the following link: <https://support.atlassian.com/statuspage/docs/enable-subscribers/> ?\n\nNicolas\n", "comments": [ { "author": "Juan Carlos Pin", "body": "Thanks [@Nicolas Grossi](/t5/user/viewprofilepage/user-id/676185) I will study that!\n" }, { "author": "Nicolas Grossi", "body": "Could you please mark the answer as accepted if you agreed ?\n\nThanks\n" }, { "author": "Juan Carlos Pin", "body": "Hi [@Nicolas Grossi](/t5/user/viewprofilepage/user-id/676185) The point is that there's nobody subscripted to it. I just need to remove it from my products :)\n\nTHX\n" } ] } ]

[ "cloud", "statuspage-cloud" ]

[ { "author": "Egor", "body": "Hey Simone, \nThanks for reaching out to Atlassian Community! \n\nThe status 5.7.1 error typically indicates that the email was refused due to a policy restriction on the receiving mail server. Here are some steps you can take to address and avoid this issue:\n\n1. **Check Email Sending Limits:**\n\nEnsure you are not exceeding the email sending limits set by your mail server or email service provider.\n\n2. **Whitelist Statuspage Email Endpoints:**\n\nAdd the Statuspage email endpoints to your mail server's whitelist to prevent them from being blocked.\n\n3. **SPF, DKIM, and DMARC Records:**\n\nVerify that your SPF, DKIM, and DMARC records are correctly configured. This helps in authenticating your emails and preventing them from being marked as unauthorized.\n\n4. **Check Email Content:**\n\nEnsure that the content of your emails complies with email sending policies to avoid being flagged as spam or unauthorized.\n\n5. **Monitor and Remove from Discarded List:**\n\nRegularly monitor your mail server's discarded list and remove any Statuspage email endpoints that may have been added.\n\n6. **Contact Email Service Provider:**\n\nReach out to your email service provider or IT team to investigate further and get detailed logs about the specific cause of the bounce messages.\n\n7. **Use a Different Email Endpoint:**\n\nIf the issue persists, consider using a different email endpoint or setting up a dedicated email account for Statuspage communications to isolate and troubleshoot the problem.\n\nThank you, \nEgor\n", "comments": null }, { "author": "Nicolas Grossi", "body": "[@Simone Maccagni](/t5/user/viewprofilepage/user-id/5521098) Welcome, as far as i know, hard bounce rejects are caused for non existing email address or user.\n\nCould you please check that ?\n\nNicolas\n", "comments": [ { "author": "Simone Maccagni", "body": "Thanks Nicolas. I'm not referring to subscribers notification.\n\nWe linked our services to status page with the email automation, our monitoring systems are sending emails to status page reporting the status of our services.\n\nWe saw once that the emails sent from our monitoring system to status page bounced back. Hope this clarifies the situation.\n" } ] } ]

[ { "author": "Egor", "body": "Hey Nelson, \nThanks for reaching out to Atlassian Community! \n\nCurrently, there is no direct way to assign specific components to be managed by certain user groups within Statuspage. The permissions model in Statuspage allows you to assign team members different roles (Admin, Viewer, etc.), but these roles apply to the entire page, not specific components.\n\nFor your use case, you might need to manage this outside of Statuspage by setting clear internal processes and guidelines for the different groups and their responsibilities, or by using multiple pages for different groups if the separation is critical. \n\nBest Regards, \nEgor\n", "comments": [ { "author": "Nelson Ngamsuntikul", "body": "Thanks Egor, for the reply; is there a reason for why it's designed this way? Are there some resources to guide me on the 'outside' processes/guidelines others use in my situation? Thanks again\n\nStatusPage Newbie,\n\nNelson\n" }, { "author": "Egor", "body": "Hey Nelson,\n\nStatuspage's design aims for simplicity and security, ensuring that only designated team members have control over the entire page to maintain consistency and prevent misuse of permissions. \n\n**Guidelines for Outside Processes:**\n\n1. **Documentation:** Maintain a shared document to track which team members manage specific components.\n\n2. **Internal Communication:** Use tools like Slack or Teams to set reminders for component owners.\n\n3. **Automation:** Implement custom scripts or use automation tools to notify owners of their responsibilities.\n\nThank you, \nEgor\n" } ] } ]

[ "cloud", "statuspage-cloud" ]

[ { "author": "Egor", "body": "Hello There and thanks for reaching out to Atlassian Community! \n\nMay I ask you please to reach out to us using the following link, so that we can assist you better? <https://support.atlassian.com/contact/> \n\nThank you,\n\nEgor\n", "comments": null } ]

[ "cloud", "statuspage-cloud" ]

[ { "author": "Jesse Klein", "body": "Hello there,\n\nThis is Jesse from the Statuspage support team. Thanks for reaching out about adding a last updated time to Statuspage. Welcome to the community. It's likely possible to accomplish this but I don't really have any specific information on what you would need to do.\n\nOne thing I found is that the last update from an incident is shown on the\n\n\\<div class=\"incident-data incident-container\"\\>\n\nMaybe you can utilize that in your custom code similar to how you might have removed incidents altogether. Beyond that, though, I don't have any practical way to accomplish this with custom code. Hopefully, this points you in the right direction.\n\nRegards, \nJesse\n", "comments": null } ]

[ "cloud", "statuspage-cloud" ]

[ { "author": "Emma Kelly", "body": "Hi all\n\nI have the same question, but the error I am getting is different! I am looking forward to solve this problem.\n", "comments": null }, { "author": "Kevin Patterson", "body": "Hi Neil,\n\nis the message you are looking to display static text?\n\nIf it is a static message One way to solve this would be to leverage the Customize HTML/CSS feature of statuspage. Using this method you will need to add the static message to the custom html header section of the page, it can looks something like below:\n\n*\\<div id=\"timedMessage\" style=\"display:none; text-align:center; padding: 10px; background-color: #ffffff;\"\\>*\n\n*\"Your display message here\"*\n\n*\\</div\\>*\n\nNext you will need to add a javascript that will handle the visibility of the message inside of your timedMessage div above into the custom footer HTML section of the screen. This should give you what you are looking for.\n", "comments": null } ]

[ { "author": "John M", "body": "Hi [@Liam Hennessy](/t5/user/viewprofilepage/user-id/403550) ,\n\nSince SPF and DKIM both pass individually, the issue likely lies in domain alignment. The DKIM is passing with Sendgrid, but the 'from' address is statuspage.io - which is likely causing a DMARC failure due to the misalignment.\n\nIf you can reach out to DigitalOcean and have them contact Statuspage support, we can look deeper into the matter, with their account access.\n", "comments": [ { "author": "Liam Hennessy", "body": "Thanks John, I'll do that.\n" } ] } ]

[ "dmarc" ]

[ { "author": "Jesse Klein", "body": "Hi Atul,\n\nThanks for reaching out. I can't see into your org structure but it looks like this is related to the fact that you're not a billing admin: <https://support.atlassian.com/subscriptions-and-billing/docs/understand-billing-administration/>\n\nIt's possible you're a product admin but not a billing admin. I would take a look at the above and see if that helps you. If not, please reach out to support.atlassian.com and open a billing issue and our customer advocate team can help you understand why you're not showing up as an admin. Hopefully, that helps!\n\nRegards, \nJesse\n", "comments": null } ]

[ "activate", "administration", "cloud", "help", "statuspage-cloud" ]

[ { "author": "Chris DeGidio", "body": "Hi, [@Jorge Armando Rodr?guez bonilla](/t5/user/viewprofilepage/user-id/5441001), this is a very specific problem related to your account. So that we can properly pull up all details and information please submit a support ticket at support.atlassian.com. Please select the billing option.\n\nThanks so much!\n\n- Chris\n", "comments": null } ]

[ "cloud", "statuspage-cloud" ]

[ { "author": "SBotalov", "body": "resolved the problem via browser_cookie3 python library which takes cookies of the current session from the browser. so I passed cookies with post request\n\ncookies = browser_cookie3.chrome(domain_name='lp-uat.luxoft.com') #get current cookies from the browser \ncookies_dict = requests.utils.dict_from_cookiejar(cookies) #convert cookies to dict\n\nr = requests.post(crowd_url, json=payload, cookies=cookies_dict)\n", "comments": null } ]

[ { "author": "Craig Castle-Mead", "body": "Hi [@jihwan Park](/t5/user/viewprofilepage/user-id/4345009)\n\nAssuming that you're talking about adding a standard Crowd Directory in Bitbucket's User Directory setup, then yes, Crowd on a server license and BB on DC should work fine (this assumes that the Bitbucket instance can talk to the Crowd server and all the other standard setup/network questions) - there should be no issues based on the different license types.\n\nCCM\n", "comments": null } ]

[ "server" ]

[ { "author": "Craig Castle-Mead", "body": "Hi [@Dawn Cooper](/t5/user/viewprofilepage/user-id/734102)\n\n\"Then that same AD group I need to restrict from everything else to prevent any crossover.\" - can you give any more context about what \"everything else\" is?\n\nYour proposed LDAP filter would/should block that group from being exposed to Crowd, you can only implement LDAP filters on a per directory basis in Crowd, so if you wanted to let users in ADGroupname to authenticate to Jira, you would either need to have two Crowd directories (on excludes this group, one includes only this group), and then map those directories to the relevant application(s), or - depending on what \"everything else\" is - let's say you've got Confluence and Bitbucket connected to the same Crowd server and you don't want these users using either of those apps, you'd leave the \"allow all users to authenticate\" option unchecked on the Conf+BB Crowd Application pages, and then select the relevant group(s) of users that represent \"the rest\" of the company. \n\nCCM\n", "comments": null }, { "author": "Dawn Cooper", "body": "I figured out a plan, I will use different local groups in Crowd with auto assignment based on an AD group and then apply the local groups in my permissions schemes.\n", "comments": null } ]

[ "active-directory", "jira", "server" ]

[ { "author": "Dai Zhang", "body": "contacting the backend smtp service provider, and they said the connection broke when sending 6 bytes in DATA stage. The mail server side could only read out 6 bytes then wait until timeout.\n", "comments": [ { "author": "Dai Zhang", "body": "It seems the crowd application does not send the SMTP commands correctly. How to debug it and fix it.\n" }, { "author": "Rinat Vafin", "body": "Hello. Have you find solution for this issue? I'm getting same behavious on using gmail smtp (and some other public relays).\n" } ] } ]

[ "smtp" ]

[ { "author": "Ashwini_More _miniOrange", "body": "Hey [@Rodrigo Kondo Fernandes](/t5/user/viewprofilepage/user-id/3524692),\n\nYou can use **[miniOrange SCIM App for Crowd](https://marketplace.atlassian.com/apps/1229918/mo-scim-provisioning-user-group-sync-for-crowd?hosting=datacenter&tab=overview)** to sync users in the crowd from Oracle IDCS. Oracle IDCS supports SCIM Protocol, which is used to set up the provisioning.\n\nThe app allows you to create, update and deactivate crowd users as per changes in the user's profile in Oracle IDCS. You can also add or remove group membership in the crowd as permissions/groups change in Oracle IDCS.\n\nYou can evaluate the app from Atlassian Marketplace directly or reach out to the miniOrange Support Portal **[here](https://miniorange.atlassian.net/servicedesk/customer/portal/2)**for demo/setup support.\n\nps: I work for [miniOrange](https://marketplace.atlassian.com/vendors/1213308/miniorange), one of the top SSO vendors in Atlassian Marketplace.\n", "comments": null } ]

[ "integration", "oracle", "user" ]

[ { "author": "Craig Castle-Mead", "body": "Hi [@colorfingers](/t5/user/viewprofilepage/user-id/5175910)\n\nTheres quite a lot of detail missing from your explanation, so the below may not be relevant for your org/setup, but some thoughts:\n\n* Crowd licenses are about users in a directory - not just who has logged in.\n* assuming you downstream Crowd server is using a Remote Crowd directory to pull users from the Upstream Crowd server, you can limit the users who are being exposed between the two instances by adjusting the \"Who can login\" options for the upstream Crowd application that the downstream Crowd directory uses. You would have to uncheck the \"anyone can authenticate\" checkbox and then add group(s) that represent your subset of users. You then need to set \"All groups, but only users with access rights\" option as per [https://confluence.atlassian.com/crowd/syncing-users-based-on-their-access-rights-1085203681.html#:\\~:text=When%20you%20map%20a%20user,is%20redundant%20in%20most%20cases](https://confluence.atlassian.com/crowd/syncing-users-based-on-their-access-rights-1085203681.html#:~:text=When%20you%20map%20a%20user,is%20redundant%20in%20most%20cases). This would only expose the users in the selected groups to your downstream Crowd server.\n\nCCM\n", "comments": null } ]

[ { "author": "Mahesh Shinde", "body": "Hi [@Mayur Jadhav](/t5/user/viewprofilepage/user-id/4290135) ,\n\nCould you please answer below queries:\n\n* The IP address which is mentioned in the error, is it Load Balancer IP address of Jira?\n* did you add IP or hostname of Jira's LB into Crowd configuration in Applications -\\> app -\\> Remote Addresses ?\n\nThis will provide you some background on this.\n\nAs you have Crowd DC setup with 2 nodes, then you have to use Crowd URL in user directory config in Jira that URL should be link with LB and LB should redirect traffic based on the parameters which is present in configuration.\n\nHere is the reference article: <https://confluence.atlassian.com/enterprise/load-balancer-configuration-options-935383760.html>\n\nRegards,\n\nMahesh Shinde\n", "comments": [ { "author": "Mayur Jadhav", "body": "Hello [@Mahesh Shinde](/t5/user/viewprofilepage/user-id/2230848) ,\n\nThanks for your response!!\n\nThe IP address which is mentioned in the error is not load balancer IP of Jira.\n\nYes, I have added and tested it, but still the same.\n\nYes, want the same configuration but unable to do it.\n\nRegards, \nMayur\n" }, { "author": "Mahesh Shinde", "body": "Hi Mayur,\n\nThe error message is corresponding to that the crowd is not authorizing the request coming from the IP 1 for \"jira-app\", it means this IP is corresponding any of the application.\n\n* Do you have any idea about this IP, to which application it has, I think it is public IP\n* Have you tried to add this IP (in error message) in Crowd configuration in Applications -\\> app -\\> jira-app -\\> Remote Addresses ?\n\nRegards,\n\nMahesh Shinde\n" }, { "author": "Mayur Jadhav", "body": "Hello [@Mahesh Shinde](/t5/user/viewprofilepage/user-id/2230848) ,\n\nThis Ip is frequently changing and even I have added and sometime the connection got successful and when I click in save and test then it again fails.\n" }, { "author": "Mahesh Shinde", "body": "Hi Mayur,\n\nI think, you have to add hostname or URL of that IP as its changing frequently.\n\nRegards,\n\nMahesh Shinde\n" } ] } ]

[ "integration", "jira", "sso" ]

[ { "author": "lamella", "body": "This is the configuration of nginx\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/243589i7C2DC942C940CD80/image-size/large?v=v2&px=999 \"image.png\")\n\nAnd this is the server.xml configuration in crowd's docker container\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/243590iACE5845B16A7DD25/image-size/large?v=v2&px=999 \"image.png\")\n\nAnd this is the rest api where crowd has \"XSRF check failed\" exception\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/243591i3C1836AA50829FE0/image-size/large?v=v2&px=999 \"image.png\")\n", "comments": null } ]

[ { "author": "Nic Brough -Adaptavist-", "body": "Did you restart the server?\n", "comments": null } ]

[ "server" ]

[ { "author": "Craig Castle-Mead", "body": "Hi [@Jakob KN](/t5/user/viewprofilepage/user-id/1204559)\n\nI'm not sure if you can really achieve what you're after, but the way I'd approach it (in testing, on a non-prod environment \\</disclaimer\\> )\n\n1. Setup a Crowd directory with two applications linked to it (one you use for SAML, one you use for \"traditional\" Crowd auth) use the \"Groups that can authenticate\" option to limit which set of users could authenticate to each type of app, setup your Jira/Confluence User Directories pointing to Crowd\n2. Then setup <https://jira.company.com/plugins/servlet/authentication-config> to give you SAML auth, one issue we had with this type of approach (in testing):\n 1. This would give your users a choice of which directory they needed to login via, and may be confusing\n\nCCM\n", "comments": null } ]

[ { "author": "Craig Castle-Mead", "body": "Hey [@Bastian Stehmann](/t5/user/viewprofilepage/user-id/1186496)\n\nI'm not aware of any GDPR functionality in Crowd (native or on the marketplace). <https://confluence.atlassian.com/gdpr/crowd-right-to-erasure-949761091.html> does have some information on where PII may be stored in the database - even if you anonymise the user entry itself.\n\nCCM\n", "comments": [ { "author": "Bastian Stehmann", "body": "Hi Craig,\n\nThanks a lot. This is helpful, but still looking for a solution with the combination of tools.\n" } ] } ]

[ "confluence", "data-center", "gdpr", "jira", "lifecycle", "server", "user", "user-management" ]

[ { "author": "Charlie Misonne", "body": "The Windows version itself should not be a problem. Crowd runs on Java so you need to make sure the Java version that Crowd 2.7.2 supports can run on your new Windows version. For Crowd the JDK is necessary (not just the JRE)\n\nI was ableto find the [*supported plaforms*page for v2.7.2](https://confluence.atlassian.com/display/CROWD027/_System+Requirements+-+Software)Since that version Crowd can run on Java 8 and according to [this page](https://www.java.com/en/download/help/sysreq.html) Windows Server 2022 supports Java 8.\n\nSo you can definitely give it a shot. But as always: try it on e testr environment first :-)\n", "comments": [ { "author": "Shraddha Sudheendra", "body": "Thank you for the answer! It helps :)\n" }, { "author": "Charlie Misonne", "body": "You're welcome!\n\nPlease mark it as accepted if it solves your question. Or don't if you need more info.\n" } ] } ]

[ "server" ]

[ { "author": "Craig Castle-Mead", "body": "Hi [@Aaron_Khan](/t5/user/viewprofilepage/user-id/5129293) ,\n\nAccessing any content via the database is never the recommended option. There may be changes to the structure with version upgrades, you'd need to reverse engineer the structure of the tables to figure out how to extract the right information - safely and reliably.\n\nThere may be an existing Marketplace app that does what you're looking for too, not sure if you've checked out that path. \n\nThat being said, sometimes certain data you need/really want is not exposed via a REST API, so you're left with two options.\n\n1 - the \"proper\" way, build your own add on that uses the relevant Java APIs to extract the data and then expose this via a REST API\n\n2 - access the data via the database, only use read only access when doing this, never write changes back to the database as this will only cause issues and headaches. This approach is at your own risk.\n\nCCM\n", "comments": null } ]

[ "api", "database", "login", "rest", "rest-api", "user" ]

[ { "author": "Craig Castle-Mead", "body": "Hi [@Jacob Dokos](/t5/user/viewprofilepage/user-id/4876544)\n\nYou're not able to see this data via the UI, there's no \"Member Of\" type of output.\n\nYou can query the cwd_membership table from the database, but this approach is at your own risk.\n\nCCM\n", "comments": null }, { "author": "Nic Brough -Adaptavist-", "body": "Atlassian stuff works on a flattened basis - group within group can be set up in Crowd, but the rest of the applications ignore it. So there's no reporting on it. You will have to look at the Crowd settings to work this out.\n", "comments": null } ]

[ "server" ]

[ { "author": "Craig Castle-Mead", "body": "Hi [@KB](/t5/user/viewprofilepage/user-id/1192464)\n\nBulk deleting users could also be done by writing a bash (or powershell, or batch) script that loops through your list of users and calls the delete REST API for each user.\n\nTake a look at the miniOrange offerings as [@Harshit bhagat](/t5/user/viewprofilepage/user-id/5106032) mentioned though. We use a number of their products and have found the pricing reasonable and support has been excellent. We have not used the Premium Bulk Use Management for Crowd.\n\nCCM\n", "comments": null }, { "author": "Harshit bhagat", "body": "Hello Kishore, \n\nI am Harshit from miniOrange Business Team. \nWe do provide the functionality of uploading a CSV or an excel in our **Premium Bulk User Management for Crowd** plugin. \n\nPlease reach out to us on [email protected] or raise a support ticket [here](https://miniorange.atlassian.net/servicedesk/customer/portal/2) and we will be happy to assist you and provide you with the further steps to satisfy your requirement. \n\nLooking forward to hearing from you soon. \n\nThanks, \nHarshit.\n", "comments": null } ]

[ "server" ]

[ { "author": "Mark Higgins", "body": "Hi [@Alain Vertefeuille](/t5/user/viewprofilepage/user-id/4819811)\n\nWelcome to the comunity.\n\nTo put a picture to [@Aaron Geister](/t5/user/viewprofilepage/user-id/4585692) response:\n\n![Screenshot 2024-09-25 151242.png](https://community.atlassian.com/t5/image/serverpage/image-id/349157i3F644AEA991DEFCF/image-size/large?v=v2&px=999 \"Screenshot 2024-09-25 151242.png\")\n\nIf you have linked a space, then it may be permissions on your Confluence space?\n\nHope this helps\n\nMark\n", "comments": [ { "author": "Aaron Geister", "body": "Thanks [@Mark Higgins](/t5/user/viewprofilepage/user-id/3517340) for the assist here. Great add to show a picture.\n" } ] }, { "author": "Aaron Geister", "body": "[@Alain Vertefeuille](/t5/user/viewprofilepage/user-id/4819811) Welcome to the community. \n\nIn JSM configuration in project settings \\> Knowledge base, did you map request types to KB articles? \n\nThat should help with suggestions that populate form the summary so there are random articles populating. \nAlso, at the Help Center portal are you able to search for articles there. If not, you should map the Confluence KB space to the JSM project. \n\nHere is tutorial from Atlassian \n[Using Confluence and Jira Service Management Together (atlassian.com)](https://www.atlassian.com/software/confluence/resources/guides/extend-functionality/confluence-jsm#overview) \n", "comments": null } ]

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

[ { "author": "Rudy Holtkamp", "body": "Hi [@Ghata Singhal](/t5/user/viewprofilepage/user-id/5370834) ,\n\nYou can do this more easily via Jira automation.\n\nIn site B you can create an automation rule which listens to a webhook and create the update/a new issue with the provided payload.\n\nIn site A you create an automation rule that triggers on a certain event (e.g. a change of status) this rule will then call the webhook of site B with a payload of the change \\& (very important) the original key of the issue.\n\nThis key is used in the first rule to determine if there is already an issue with that key, if so it will create the comment, if not it will create a new issue with all the info you provided in the payload.\n", "comments": [ { "author": "Ghata Singhal", "body": "Thank you for replying.\n\nI figured webhooks would a way around this problem. Is there any detailed use case with solutin for refeence? I have never worked on webhooks before and seems a little complicated rn.\n" }, { "author": "Rudy Holtkamp", "body": "I'm sorry I don't have a detailed use case typed out.\n" } ] } ]

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

[ { "author": "Francisco Torrecillas Sabater", "body": "Hi everyone!\n\nI wanted to share that I've finally resolved the issue with the dependent dropdown for degrees based on the selected university.\n\nThe key was in configuring the AQL correctly in the custom fields for \"Universities\" and \"Degrees.\" Here's what I did:\n\n1. **In the \"Degrees\" field** (the dependent dropdown), under **Filter Scope (AQL)**, I set the following:\n\n `objectType = `\"Titulaci?n\"` `\n\n This ensures that only objects of type \"Degree\" are displayed in the field.\n2. In **Issue Scope of the Filter (AQL)**, I added this condition:\n\n `Universidad = `${customfield_10203}` `\n\n This filter ensures that only the degrees related to the selected university in the \"Universities\" field (customfield_10203) are displayed in the \"Degrees\" dropdown.\n\nWith this setup, when I select a university in the first dropdown, only the corresponding degrees appear in the second dropdown.\n\nIf anyone is facing a similar issue, I hope this solution helps! Thanks again for all the support.\n", "comments": null } ]

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

[ { "author": "Robert DaSilva - Adaptavist", "body": "Hi [@Luis Felipe Viana](/t5/user/viewprofilepage/user-id/5438757) ,\n\nThe \"Raise a request on behalf of someone\" should only be showing up for users who also have JSM Agent privileges. Regular Customers (those with only the JSM Customer) permission should not have this option.\n> Customers are unable to raise a requests on behalf of another customer, but admins or agents may raise a request on a customer's behalf in two ways.\n\n[Here's a link to that Atlassian Documentation.](https://support.atlassian.com/jira-service-management-cloud/docs/raise-a-request-on-behalf-of-a-customer/#:~:text=Customers%20are%20unable%20to%20raise%20a%20requests%20on%20behalf%20of%20another%20customer%2C%20but%20admins%20or%20agents%20may%20raise%20a%20request%20on%20a%20customer%E2%80%99s%20behalf%20in%20two%20ways.)\n\nAre you accidentally giving all of your users the \"Agent\" permission, instead of plain Customer? Agent is usually only given to those who will action tickets raised in a JSM project, so not everyone at your organization requires this. Instead, the \"JSM Customer\" permission lets those users raise tickets.\n\nHope that helps,\n\nRobert\n", "comments": null } ]

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

[ { "author": "Owen Pyatt", "body": "????????, ??? ????????? ???????? ????? ?????????? ? ???????????? ? ???????????? ????? ???????. ?? ?????? ?????????? ????????? ????????? ????????????? ? ?????????? \\<\\<????????? ?????????\\>\\> ? ????? ????? ??????????, ????? ?????????????, ??? ?????? ????????? ???? ?????? ??????? ???????.\n\n???????? ?????????? ???????? ?? ?????????? ?? ?????????? ???????? ? ?????, ?? ?????????? ?? ? ?????? ????? ??????? ?????? ???? ????????.\n\n??? ??????? ???????:\n\n1. ????? ?????????? ????? ???? ?????? ??? ?????? ????????, ??????? ?????????, ??? ?? ??????, ??? ????????? ? ????? ??????? ????? ????? ???????? ?? ?????? ???????.\n\n2. ?????????, ??? ?? ?? ???????????? ????? ?????????? ?? ?????????. ???? ?? ?????? ??????????? ????? ?? ?????????, ? ????? ??????????????? ????????????? ????? ? ??????? ?? ? ?????????? ????????.\n\n??? ????? ????????? ?????? ? ???, ??? ??????? ????????? ? ???? ????? ??????????.\n\n[??????? ?? ????? ??????????](https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/)\n", "comments": null } ]

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

[ { "author": "Natalya Ozhigova", "body": "Hi [@Niclas Moberg](/t5/user/viewprofilepage/user-id/5600463)\n\nAs I see, it has not implemented yet. Atlassian has a ticket with suggestion to implement this:\n\n<https://jira.atlassian.com/browse/JSDCLOUD-2517>\n\n(<https://jira.atlassian.com/browse/JSDCLOUD-4140>)\n\nYou can allow to create a portal-only accounts for all users or if you won't like to allow this, you can use a plugins from Atlassian Marketplace. Some plugins allow to send a response to customer if the ticket isn't created.\n\nBest regards\n\nNatalya\n", "comments": null }, { "author": "Sravan Indukur", "body": "Hi [@Niclas Moberg](/t5/user/viewprofilepage/user-id/5600463) ,\n\nGreetings of the day.\n\nYou can achieve this in two ways:\n\n1. **Using Automation** (Allows for customization of notifications)\n2. **Using Email Notification Scheme** (A built-in Jira feature, with no customization---notifications will follow the standard Jira format).\n\n**For Automation:**\n\n* **Trigger:** Issue created\n* **Condition:**\n * JQL Condition: `\"request type\" = \"Emailed request (Project Key)\"`\n * Or Field Condition: \n Field = Request Type \n Condition = Equal \n Value = \"Email Request\"\n\n**For Notification Schemes:**\n\n* Navigate to **Project Settings** \\> **Notifications**\n* Click on **Actions** \\> **Edit Notifications**\n* Under \"An Issue is Created,\" add the roles, groups, or individual users as per your requirements.\n* Refer the below link : <https://support.atlassian.com/jira-cloud-administration/docs/configure-notification-schemes/>\n\nRegards,\n\n[@Sravan Indukur](/t5/user/viewprofilepage/user-id/5301477)\n", "comments": [ { "author": "Niclas Moberg", "body": "Hi [@Sravan Indukur](/t5/user/viewprofilepage/user-id/5301477)\n\nThank you for your response!\n\nHowever, this doesn't solve my issue.\n\nThe problem is that some senders aren't registered as customers. Since Channel access is set to Restricted access, these emails won't create an issue to start with.\n\nWe want to keep it that way to be able to control who is granted access and not. But there has to be some way to notify the sender that they aren't granted access.\n\nAs it is now, nothing happens at all. The customer does not receive confirmation that the issue has been created, because the issue has not been created. But they also don't get a message that it hasn't been created because they don't have permission.\n" } ] } ]

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

[ { "author": "Mark Higgins", "body": "Hi [@Karim Mohamed](/t5/user/viewprofilepage/user-id/5046408)\n\nWe have implemented a Level 2 Approver using Assets.\n\nExample:\n\nSoftware Catalog:\n\nApproval Required: True / False\n\nApprover: User\n\nL2 Approval Required: True / False\n\nL2 Approver: User\n\nWe then use automation/assets and a L2 Status to achieve a 2nd level of approval.\n\nHope that helps\n\nMark\n", "comments": null }, { "author": "Jim Knepley - ReleaseTEAM", "body": "I think you'll need to use ScriptRunner and the UserPropertyManager API. With ScriptRunner, you can implement whatever business logic you like and set an \"Approver\" field that you would use for the approval configuration.\n", "comments": null } ]

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

[ { "author": "Rudy Holtkamp", "body": "Hi [@Daniel_Adersteg](/t5/user/viewprofilepage/user-id/3650288) ,\n\nNo you can't link it directly.\n\nHowever you can create a satisfaction form and make a 'Star' form field, rating 1 to 5. After the user submits the form, you can trigger an automation which calls the REST API end point (<https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-requestidorkey-feedback-post>) where you can add the Atlassian default CSAT scores.\n\nI hope this helps.\n\nRudy\n", "comments": null } ]

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

[ { "author": "Anusha A", "body": "Hi Camila,\n\nThanks for your question on community.\n\nUsing **Issue Collectors** in Jira is a great way to create tickets from unregistered users on an external page.\n\nAn Issue Collector is a feature in Jira that allows you to embed a form on your website, enabling users to submit issues directly into Jira without needing an account. More information on Embedding an issue collector into your website is here -\n\n* <https://support.atlassian.com/jira-cloud-administration/docs/use-the-issue-collector/>\n\nAt the moment, this is available **only** for Company Managed Projects however we have been tracking a feature request with our developers requesting the implementation on Team managed projects. Here is the reference for you to vote and watch -\n\n* <https://jira.atlassian.com/browse/JRACLOUD-76487>\n\nHope this is helpful.\n\nRegards,\n\nAnusha A\n", "comments": null }, { "author": "Vijay Dadi", "body": "Hello [@Camila Lorena Reyes](/t5/user/viewprofilepage/user-id/5464154) ,\n\nThe best way to create an issue for external users is to have a default account and pass that in the payload. Hope this helps\n\nVijay\n", "comments": null } ]

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

[ { "author": "Perumal M", "body": "Hi [@Sreenivasulu](/t5/user/viewprofilepage/user-id/5571166) ,\n\n\"Could you please use the script below in Scriptrunner behavior? It will be helpful for you.\"\n\nimport com.atlassian.jira.component.ComponentAccessor \nimport com.atlassian.jira.security.roles.ProjectRoleManager\n\n// Get the Project Role Manager \ndef projectRoleManager = ComponentAccessor.getComponent(ProjectRoleManager) \ndef financeRole = projectRoleManager.getProjectRole(\"Finance\") // Replace with your actual project role name\n\n// Get the current user and project \ndef currentUser = ComponentAccessor.jiraAuthenticationContext.loggedInUser \ndef project = issueContext.projectObject \ndef totalRevenueField = getFieldById(getFieldChanged())\n\n// Debugging: Print out the current user and project \nlog.error(\"Current user: ${currentUser.username}, Project: ${project?.key}\")\n\n// Check if the user has the \"Finance Team\" role in this project \nif (projectRoleManager.isUserInProjectRole(currentUser, financeRole, project)) { \n// Finance users: Show the field and make it editable \ntotalRevenueField.setHidden(false) \ntotalRevenueField.setReadOnly(false)\n\nlog.error(\"User ${currentUser.username} is part of Finance Team. Showing Total Revenue field.\") \n} else { \n// Non-Finance users: Hide the field completely \ntotalRevenueField.setHidden(true) \ntotalRevenueField.setFormValue(\"Empty\") \nlog.error(\"User ${currentUser.username} is NOT part of Finance Team. Hiding Total Revenue field.\") \n} \nNote: It will only support the edit and create screens. The behavior script won't directly hide the field in the view screen; you need to use the Scriptrunner fragment.\n", "comments": null }, { "author": "Chris Rainey", "body": "Hi there,\n\nCheck out these YouTube videos on Behaviors in ScriptRunner and see if they assist you.\n\n[Video 1](https://www.youtube.com/watch?v=IyOibvtZJbs)\n\n[Video 2](https://www.youtube.com/watch?v=x59UiTUyVSQ)\n", "comments": null } ]

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

[ { "author": "Rudy Holtkamp", "body": "Hi [@Lee Hutchinson](/t5/user/viewprofilepage/user-id/5572101) ,\n\nDid you create the user group in the admin console?\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/348998i7248D8094B6F5082/image-size/large?v=v2&px=999 \"image.png\")\n\nThen go to the request types \\> click on the lock icon \\> type Staff\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/348999i83096D5514732F15/image-size/large?v=v2&px=999 \"image.png\")\n\nThis should work.\n", "comments": [ { "author": "Lee Hutchinson", "body": "I created the group and added members in admin, but when I go back to the project and try start typing the group name nothing appears\n" }, { "author": "Rudy Holtkamp", "body": "That is very strange, it should be available. Maybe a caching issue in your browser\n" }, { "author": "Kieren _SmolSoftware_", "body": "Hi [@Lee Hutchinson](/t5/user/viewprofilepage/user-id/5572101)\n\nThere's often a delay between creating a group and it syncing with the JSM backend. Shouldn't be more than a few minutes at most. If you close/refresh the page, does the group show up?\n\nCan you see any other groups at all when you try to restrict to a group via the page [@Rudy Holtkamp](/t5/user/viewprofilepage/user-id/636802) posted?\n" }, { "author": "Kieren _SmolSoftware_", "body": "Some group searches can be very picky, did you search with the correct letter case? Eg capital vs lowercase\n\nDoes the group name you created have any unusual/uncommon characters?\n" } ] } ]

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

[ { "author": "Mehmet A _Bloompeak_", "body": "Hi [@Ruchi](/t5/user/viewprofilepage/user-id/5497004) ,\n\nAs far as I know the only option is using rest api and it returns JSON not CSV.\n\n<https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-organization/#api-rest-servicedeskapi-organization-get>\n\nThe rest api has pagination, it takes 50 organization on each page. You need to modify the **start** parameter if you have more than 50 organizations.\n\n```\n/rest/servicedeskapi/organization?start=1\n```\n", "comments": [ { "author": "Ruchi", "body": "Thank you [@Mehmet A _Bloompeak_](/t5/user/viewprofilepage/user-id/3740047) I tried the above suggestion but why is it giving random organisations , I was expecting to see the 1st 50 organisations.\n" }, { "author": "Mehmet A _Bloompeak_", "body": "I guess it returns the organizations ordered by their ids. The ids are generated by the organization creation date. It is not possible to get organizations ordered by name. You need to get all the organization page by page and then combine them into a single json array. Then you can sort it using javascript coding.\n" }, { "author": "Ruchi", "body": "Thank you:)\n" } ] }, { "author": "shib saha", "body": "Hi [@Ruchi](/t5/user/viewprofilepage/user-id/5497004) , Welcome to the community! There is no option available from UI to export the organization member in csv in JSM. Here is the link to the rest api for extracting the same data to csv using th erest api.\n\nHope this will be helpful to your query, in case of any query let me know. Thanks\n", "comments": [ { "author": "Ruchi", "body": "Hi Shib [@shib saha](/t5/user/viewprofilepage/user-id/4610701) Thank you:)\n\nCould you please share the link , I dont see this in your answer.\n" }, { "author": "shib saha", "body": "Apology i forgot the share the link: <https://developer.atlassian.com/cloud/customer-service-management/rest/v1/api-group-organization/#api-api-v1-organization-organizationid-get>\n" } ] } ]

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

[ { "author": "Cristian IONESCU", "body": "Hi Ruchi,\n\nIn Jira Service Management, the ability to add multiple announcements directly is limited to a single announcement that can have multiple sections.\n\nExample:\n\n![ann.png](https://community.atlassian.com/t5/image/serverpage/image-id/348928i8B3EC6A1AE2EF1E7/image-size/large?v=v2&px=999 \"ann.png\")\n\nIf you want to segregate this by groups, you might consider using the \"Send email\" function. To do this, go to Jira settings \\> System \\> Send email. From there, select the project roles, choose the relevant project from the dropdown menu, and select \"Service Desk Customers\" as the role.\n\nHope this helps.\n", "comments": [ { "author": "Ruchi", "body": "Thank you [@Cristian IONESCU](/t5/user/viewprofilepage/user-id/5123296) Looks like this is the only way to do it.\n\nThanks for bringing up \"Send email\" function I can not make use of it now as the message I want to send is for our new/unregistered users but its good to know .\n" } ] }, { "author": "Walter Buggenhout", "body": "Hi [@Ruchi](/t5/user/viewprofilepage/user-id/5497004),\n\nWhile there is one announcement message box for a help center / portal, this is a text area that you can fill with content as you like. If you would like to add long text or multiple messages in there, you should be able to do so.\n\nHope this helps!\n", "comments": [ { "author": "Ruchi", "body": "Thank you [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225) , looks like that's the only way to do it.\n" } ] } ]

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

[ { "author": "Carla Ann Rowland", "body": "go to the customer list and remove his profile and remove him from the jira user groups..\n\nThe customer roster is found on the service desk left panel --customers.\n\nThere is a jira user group that has access to the portal make sure his profile is removed from this group.\n\nIf he does not need access to your instance at all you should be able to deactivate his profile.\n", "comments": null }, { "author": "Mohamed Saad Taha", "body": "Is there any idea's\n", "comments": null }, { "author": "Manoj Gangwar", "body": "Hi [@Mohamed Saad Taha](/t5/user/viewprofilepage/user-id/4963037)\n\nUnder User Management, you can disable the user's JSM - Agent \\& Customer license.\n", "comments": [ { "author": "Mohamed Saad Taha", "body": "Hi [@Manoj Gangwar](/t5/user/viewprofilepage/user-id/4484987) ,\n\nhe is already don't have JSM license but he has access to customer portal to open requests on the projects that have this configuration in customer permissions ( Customers who have an account on this Jira site )\n\nand I don't want to allow him to open any request, and he is active directory user so i don't have any option to disable his account\n\nplease let me know if it is clear\n" }, { "author": "Manoj Gangwar", "body": "So you are not getting the option to disable the site access.\n\n![Screenshot 2024-09-24 155434.png](https://community.atlassian.com/t5/image/serverpage/image-id/348943i498B5F64DDDF47CD/image-size/large?v=v2&px=999 \"Screenshot 2024-09-24 155434.png\")\n" }, { "author": "Mohamed Saad Taha", "body": "Iam using Jira data center version, where this options?\n\nI think this is cloud only\n" } ] } ]

[ "jira-service-desk-data-center", "jira-service-management", "jira-service-management-data-center", "jira-service-management-server", "server" ]

[ { "author": "Evgenii", "body": "We have exactly the same problem. \nIt can be fixed, if admin grants assign permissions to reporter, but it's not suitable. We specially blocked such permissions. \n\nAnd it assigns reporter as assignee, even if project is configured that Assignee must be Unassigned. \n\nI think it's Atlassian bug, but I don't see open incident\n", "comments": [ { "author": "Evgenii", "body": "Made ticket. \nUPD from Atlassian Support: \n\n> I would like to inform you that we have reported this incident internally, and our team is currently working on it. We will keep you updated on the progress.\n>\n> In the meantime, if you have any questions please don't hesitate to write back and I will be glad to assist.\n>\n> Thanks for your patience and co-operation on this.\n" } ] } ]

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

[ { "author": "Cristian IONESCU", "body": "Hi Yanchiu,\n\nUnfortunately, Jira doesn't provide an out-of-the-box configuration to change the position of the field description(e.g., placing the label or description **above** the text area) in the agent portal.\n", "comments": null } ]

[ "custom-field", "jira-service-desk-data-center", "jira-service-management", "jira-service-management-data-center", "jira-service-management-server" ]

[ { "author": "Evgenii", "body": "Hi, [@GBE](/t5/user/viewprofilepage/user-id/737164)\n\n<br />\n\nThere is one more way, but it's kinda workaround ) It won't prohibit changes, but it will deal with consequences. \nYou can set automation rule, which will trigger on changing of assignee, and if field is empty - then set previous assignee. \nOr assign manager and add comment, that \"This bad person removed himself from assignee\" :)\n", "comments": null }, { "author": "Sravan Indukur", "body": "You can manage this through the Permissions settings.\n\nNavigate to Project Settings \\> Permissions and look for the Assign Issues permission. This permission is required for a user to assign tickets to others (including assigning them as unassigned).\n\nTo control this, grant the permission to administrators and remove it from project roles that should not have this ability.\n", "comments": [ { "author": "Sravan Indukur", "body": "Refer the below link:\n\n<https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/>\n" }, { "author": "GBE", "body": "If we do like this, it means that people can't assigned other people on the ticket. for a code review, for example right ?\n" }, { "author": "Sravan Indukur", "body": "yes\n" } ] } ]

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

[ { "author": "Walter Buggenhout", "body": "Hi [@Ian Robinson](/t5/user/viewprofilepage/user-id/5277555),\n\nTo refer to the triggering issue in your smart values, use {{triggerIssue.customfield_xxxxx}} instead of {{issue.customfield_xxxxx}}. The latter refers to the issue you are editing, which does not have a value (yet).\n\nHope this helps!\n", "comments": [ { "author": "Ian Robinson", "body": "ahh of course! Thanks Walter, all working now.\n" } ] } ]

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

[ { "author": "Bibek Behera", "body": "[@Lance Li](/t5/user/viewprofilepage/user-id/3751213) ,\n\nWhat I can think of from the problem description is to have a Project role created \"Resolver\" and grant those project permission to perform the required activities.\n\n<https://support.atlassian.com/jira-cloud-administration/docs/manage-project-roles/>\n\n<https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/>\n\nOn top of that the please review your existing workflow to make the changes to the Condition and Validators if those are having anything linked to the Users/Group/Field to transition the issue.\n\n<https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/>\n\nBest Regards,\n\nBibek\n", "comments": [ { "author": "Lance Li", "body": "Hi [@Bibek Behera](/t5/user/viewprofilepage/user-id/510396)\n\nThanks for your prompt input, let me be more specific, we now have the Jira Service Management data-center version installed, we have around 250 agents, and the ITSM project has been running for over 4 years, we have different groups of people under IT utilizing this tool, so I think the new management team wants to implement something I remembered for other Service Desk tools like ServiceNow called resolver groups that all the activities are dealt by the resolver group not the single assignee. which means the resolver group can be assigned the tickets or resolve the tickets and all actions or histories will be resolve groups, so resolver groups is the actual assignee.\n" } ] } ]

[ "data-center", "jira-service-desk-data-center", "jira-service-management", "jira-service-management-data-center", "jira-service-management-server", "server" ]

[ { "author": "Bibek Behera", "body": "[@Furkan](/t5/user/viewprofilepage/user-id/5216901) ,\n\nI would suggest to check for the impacted user which user and compare there group membership.\n\n<https://support.atlassian.com/jira-service-management-cloud/docs/set-up-and-manage-portal-access/>\n\n-Bibek\n", "comments": null }, { "author": "Geethanjali Katagani", "body": "Hi [@Furkan](/t5/user/viewprofilepage/user-id/5216901) ,\n\nTo allow any user to access the JSM portal, you must configure the portal as open at the project level.\n\nGo to **Project Settings** \\> **Customer Permissions** \\> set the portal to \"Open.\"\n\nIf issues persist, check the global settings.\n\nClick on the cogwheel icon on the top right, select **Products** \\> **JSM\\>customer access** , and adjust the settings accordingly. \n\n![AC1.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/348874i44DA0DB2E4490AC9/image-size/large?v=v2&px=999 \"AC1.PNG\")\n", "comments": [ { "author": "Furkan", "body": "Hello, I closed off the portal because our customers somehow found it and kept making tickets that are meant for support and not for internal support. I have added our azure ad group as a customer, hopefully this has helped\n" } ] }, { "author": "Walter Buggenhout", "body": "Hi [@Furkan](/t5/user/viewprofilepage/user-id/5216901),\n\nTo access the portal, people do **not** need a license, but they must be added as customers to your JSM project. Most likely, this was not the case for the 4 people you refer to.\n\nHope this helps!\n", "comments": [ { "author": "Furkan", "body": "Is it possible to automatically have all of my co workers as customers? I tried to make an organisation but no clue if it's possible to make an conditional access that if they have groups that come from azure that they will be automatically added as a customer / added to the organisational unit\n" } ] } ]

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

[ { "author": "Stiltsoft support", "body": "Hi [@GK](/t5/user/viewprofilepage/user-id/5574928) ,\n\nMaybe your company uses our [Table Filter, Charts \\& Spreadsheets for Confluence](https://marketplace.atlassian.com/apps/27447/table-filter-charts-spreadsheets-for-confluence?tab=overview&hosting=cloud&utm_source=atl_community&utm_medium=answer&utm_campaign=table-filter-traffic-sources&utm_vendorID=1216111) app to work with tables - please note that the plugin also provides the [Table from CSV](https://docs.stiltsoft.com/tfac/cloud/table-from-csv-42246005.html?utm_source=atl_community&utm_medium=answer&utm_campaign=table-filter-traffic-sources&utm_vendorID=1216111) and [Table from JSON](https://docs.stiltsoft.com/tfac/cloud/table-from-json-58427709.html?utm_source=atl_community&utm_medium=answer&utm_campaign=table-filter-traffic-sources&utm_vendorID=1216111) macros.\n\nThey automatically recreate tables from attachments and URLs (you change the source data and the recreated table is also updated). Please check the links to the macro descriptions given above - maybe it will help your case.\n", "comments": [ { "author": "GK", "body": "Thank you very much for the fast answer! :)\n\nAt least from my understanding of the given solutions, my use case is different. I will try to describe it better.\n\nEach docupedia page is based on same template and contains: product name, responsible, short description, block diagram, etc... For each product, we have it's own docupedia page.\n\nAssume we have csv file, which is an extract from a database and contains: product name, responsible, and short description for all the products. So the responsible and short description for each product, should be updated in the respective docupedia page which has the same title as the product name.\n\nThe block diagrams are saved in windows folders or in SharePoint. The links could be in the same csv file or in a different file. In docupedia pages, not the link, but the figure should be automatically updated.\n\nSo, in principle: information from csv file is spread in many pages, not in a table.\n\nI hope, my second description is more understandable.\n\nI am very new with Confluence, thank you very much for your support! :)\n" }, { "author": "Stiltsoft support", "body": "Theoretically, you may insert the Table from CSV macro on any page and as many pages as you need. It will grab all the data that you have in your database.\n\nAnd for each page there will be filters on top that will filter your big table and show only relevant data for each product. Once the database is updated, all the mirrored tables that you get using the Table from CSV macros are also updated and the applied filters continue to show only relevant data.\n\nBut the issue is in Sharepoint: our macro supports Google Sheets and your local databases, of course, but Sharepoint has some issues with authentication and is not supported by our app.\n\nYou may try to browse Atlassian Marketplace for some Sharepoint connectors or smth similar, because I really don't think that it is possible to achieve your case natively. And you may also create a new question with a more thorough description - maybe it will attract users with similar cases or other vendors (we also search for relevant questions here manually using the keywords).\n" } ] } ]

[ "confluence", "filter", "table", "table-filter", "table-filter-and-charts", "table-filter-charts-spreadsheets", "table-from-csv", "table-from-json" ]

[ { "author": "Eran Roiter", "body": "UP\n", "comments": null }, { "author": "Bill Sheboy", "body": "Hi [@Eran Roiter](/t5/user/viewprofilepage/user-id/5289455)\n\nPlease post an image showing the audit log details for the rule execution.\n\nNext, what do you mean by \"Father issue\"? Is that the Idea in the JPD project? If so, is this your scenario:\n\nGIVEN an issue exists in a software project \nAND that issue implements an Idea in a JPD project \nAND all other issues implementing that Idea are Done, Closed, Cancelled, (i.e., completed) \nWHEN the issue transitions to Done or Cancel \nTHEN transition the Idea to Done\n\nKind regards, \nBill\n", "comments": [ { "author": "Eran Roiter", "body": "Thanks for your time!\n\n<br />\n\nWhat you can see below is the first time a linked issue moved to done, while there's one more linked issue that is still in progress status\n\n![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/343684iA734BD6EE75264FA/image-size/large?v=v2&px=999 \"image.png\")\n" }, { "author": "Bill Sheboy", "body": "Hi, [@Eran Roiter](/t5/user/viewprofilepage/user-id/5289455)\n\nSorry for the delay in responding as I have been offline for a few weeks.\n\nDid you see my earlier questions about what is a \"Father issue\"?\n\nHow well does what I described match your scenario?\n\nAnd...please note well that links are directional, and so your related issues condition could have problems. That is, the delivery issues have link types of \"implements\" for the idea.\n\nYour rule could probably flow like this:\n\n* trigger: issue transitioned to one of your done status values\n* condition: issue type is not an Idea\n* branch: to the specific Idea, using the link type\n * related issues condition: **use only JQL** to confirm there are **no incomplete issues linked to the idea**\n * issue IN linkedIssues(\"{{issue.key}}\", \"is implemented by\") AND statusCategory != Done\n * action: transition the Idea\n\nI suggest only using JQL in the Related Issues Condition as that provides precise control of what is tested. Using the other clauses may not work as expected (as how they are combined is not documented).\n" } ] }, { "author": "Eran Roiter", "body": "![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/343176iAF0ED7F907B63B62/image-size/large?v=v2&px=999 \"image.png\")\n", "comments": null } ]

[ "done", "jira-product-discovery", "trigger" ]

[ { "author": "Bill Sheboy", "body": "Hi [@Eran Roiter](/t5/user/viewprofilepage/user-id/5289455)\n\nFor a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!\n\nUntil we see those...\n\nI hypothesize your rule is triggered on a change to the delivery issue in the software project, and that the rule scope is in that project. And so it cannot see / act on the JPD Idea.\n\nThis rule will need to have multiple-project or global-scope to access the issues in the different projects. Your Jira Site Admin will need to help do that as changing the scope configuration of a rule is a global admin feature for rules.\n\nKind regards, \nBill\n", "comments": null } ]

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

[ { "author": "Trudy Claspill", "body": "Hello [@Wing](/t5/user/viewprofilepage/user-id/5573169)\n\nWelcome to the Atlassian community.\n\nWhen asking for help with an Automation Rule it will make it easier for us to help you if you show us screen images of your complete automation rule with details of each step.\n\nOtherwise, refer to this documentation which includes an example:\n\n<https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Multi-user-picker-custom-field>\n", "comments": null }, { "author": "Rick Westbrock", "body": "My first thought is that you need to enclose the two values in square brackets (aka put them in a list) similar to how they were returned. I think that typically this is how multiple values are added to a field:\n\n```\n\"customfield_10002\": [{\"id\": \"652354565fvf56585cggh\"}, {\"id\": \"45628456ghkg55668ghh\"}]\n```\n", "comments": null } ]

[ { "author": "Bill Sheboy", "body": "Hi [@Ryan teo](/t5/user/viewprofilepage/user-id/5572948) -- Welcome to the Atlassian Community!\n\nThat is possible using the Issue Created trigger and rule conditions to check the fields, perhaps using an if / else condition for the different paths.\n\nI recommend reviewing the documentation basics for rules and smart values, and then trying to create your rule. If you run into challenges, post images of your complete rule and the audit log details, and explain what is not working as expected.\n\nTo get you started on creating your rule, please refer to these documentation and example sources:\n\n* <https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation>\n* <https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/>\n* [https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all\\&page=1\\&pageSize=20\\&sortKey=name\\&sortOrder=ASC](https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all&page=1&pageSize=20&sortKey=name&sortOrder=ASC)\n* <https://support.atlassian.com/jira-software-cloud/docs/use-advanced-search-with-jira-query-language-jql/>\n\nKind regards, \nBill\n", "comments": null } ]

[ { "author": "Matt", "body": "If it's a real mail account, can your admin set up mail forwarding to forward that new account to your account? This way, you'll receive the invite email and then be able to move forward with token creation. Once it's all set up you can disable the mail forwarding.\n", "comments": [ { "author": "Trudy Claspill", "body": "Note that Organization Admins cannot create an API token on behalf of another user.\n\nYou must login as the user itself to make an API token for a user.\n" }, { "author": "Matt", "body": "Yes! That is an important detail to note.\n" } ] } ]

[ "jira", "token", "users" ]

[ { "author": "Bill Sheboy", "body": "Hi [@Satty](/t5/user/viewprofilepage/user-id/5567089)\n\nAre you using a marketplace addon for Confluence content archiving? If so, you may want to check that product's documentation to see what automation capabilities are available to support your needs.\n\nKind regards, \nBill\n", "comments": null } ]

[ { "author": "Bill Sheboy", "body": "Hi [@Matt Caruso](/t5/user/viewprofilepage/user-id/5569167) -- Welcome to the Atlassian Community!\n\nShort answer: no. Within an iterator, no other data is visible.\n\nFor your scenario, there are a few workarounds, and the simplest one may be to not use the lookup table. Assuming your lookup only contains those types, you could do this:\n\n```\n*Completed this week:*\n{{#lookupIssues}}\n:jira-{{issueType.name.toLowerCase()}}: <{{url}}|{{key}}>: {{summary}}\n{{/}}\n```\n\nKind regards, \nBill\n", "comments": [ { "author": "Matt Caruso", "body": "Brilliant! That worked perfectly.\n" } ] } ]

[ { "author": "Adolfo Casari", "body": "[@Davyd Derkach](/t5/user/viewprofilepage/user-id/5550816)You can include all data you need in the json payoad.\n\nTake a look to this:\n\n<https://confluence.atlassian.com/jirakb/working-with-incoming-webhook-data-in-automation-for-jira-1125878776.html>\n", "comments": [ { "author": "Davyd Derkach", "body": "[@Adolfo Casari](/t5/user/viewprofilepage/user-id/853257)\n\nThanks for your reply. I am already using **`{{webhookData}}`** `` smart value to parse my webhook body.`` \n\n``But my question is other: Is in my case it`s a correct way to use a script that sends the Jira Issue keys t``hat related to current release`` to my automation rule via webhook like this:`` \n\n*curl -X POST -H 'Content-type: application/json' --data '{\"data\": {\"keys\":*`` \"BDO-392,BDO-391\"}}'``<https://automation.atlassian.com/pro/hooks/>``<your-webhook>`` \n\n``Maybe it`s possible to not use script and get all needed values:`` \nRelease Engineer name, release date and Jira Issues keys that related to current release?\n" } ] } ]

[ "gitlab", "integration", "smart-value", "webhook" ]

[ { "author": "John Funk", "body": "Hi Sanjay,\n\nI would create two separate rules - that should make number 4 very easy then. You can add it to the existing one, then copy the rule and adjust for the other trigger.\n", "comments": [ { "author": "Sanjay Dangi", "body": "Hello John,\n\nWhat do i need to do to create a separate rule for 4? If you can guide me please\n" }, { "author": "Bill Sheboy", "body": "Hi [@Sanjay Dangi](/t5/user/viewprofilepage/user-id/5451233)\n\nIn addition to John's suggestions...\n\nThere are two errors in your current rule in the Send Email action's content: in the triggering issue line, the URL and summary are instead referring to the Epic as they are missing the {{triggerIssue}} prefix.\n\nConsider changing that line to this:\n\n```\nTriggering Issue: {{triggerIssue.key}}?{{triggerIssue.url}} and summary -?{{triggerIssue.summary}}\n```\n\nKind regards, \nBill\n" }, { "author": "Sanjay Dangi", "body": "Thank you bill for the suggestions.\n\nCould you also suggest as to how should I go for #4!!\n\nThanks again,\n\nSanjay\n" }, { "author": "Bill Sheboy", "body": "*First thing, I am using Jira Cloud and not Server / Data Center, and that is what you are apparently using. Please investigate your version and test accordingly. With that out of the way...*\n\nWhen using the multiple events trigger as you show, the rule has less information available. Try using the specific triggers to gain more information...\n\nIf you use the Issue Moved trigger instead, you at least know the issue was moved from another project. For Jira Cloud, the smart value expression {{#changelog.project}}{{fromString}}{{/}} will indicate the source project. I do not know if that works for Server / Data Center.\n\nWhen issues are Cloned with Jira Cloud, a clones link is added. If that also applies with Jira Server / Data Center, the link could be used to identify the source issue when the Issue Created trigger is used.\n" }, { "author": "Sanjay Dangi", "body": "Thank you Bill\n" } ] } ]

[ "cloud", "jira" ]

[ { "author": "Bill Sheboy", "body": "Hi [@Serge Kravchenko](/t5/user/viewprofilepage/user-id/5567547) -- Welcome to the Atlassian Community!\n\nIn my experience, some smart value content in automation rules which appears to be JSON or list values is neither of those things. The only way to know is to attempt to parse them.\n\nHave you tried using list operations on your specific issue property?\n\nIf that did not work, have you tried using match() or split() to transform the values into a list?\n\nIf you only need the number of properties for a specific issue, perhaps call the REST API endpoint to get the property keys: <https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-properties/#api-rest-api-3-issue-issueidorkey-properties-get>\n\nKind regards, \nBill\n", "comments": [ { "author": "Serge Kravchenko", "body": "Hi Bill, thank you so much for your response! \nYep, I tried using list properties such as size and string methods such as match(). Neither of them worked, so I concluded that the value is a JSON object. :( \n" }, { "author": "Bill Sheboy", "body": "The match() could be encountering challenges if there are any embedded formatting characters in the content, such as newlines causing the regular expression to halt processing. One workaround for that is to replace such characters prior to match attempts.\n\nWithout seeing the specifics of the content in that smart value, I recommend reviewing it to identify where / on-what a split() could be used to produce a list.\n" }, { "author": "Serge Kravchenko", "body": "Hi Bill, I don't think any of these methods are available for a JSON object which {{issue.properties}} seems to return. I tried them, they don't return anything.\n" }, { "author": "Bill Sheboy", "body": "It is unclear to me of that smart value always contains JSON or if it is plain text. If it is JSON and contains a list, it should be capable of iteration and list function usage.\n\nI recommend writing the smart value to the audit log, then experimenting by picking text within the result to use with the split() function.\n" }, { "author": "Bill Sheboy", "body": "Hi [@Serge Kravchenko](/t5/user/viewprofilepage/user-id/5567547)\n\nJust checking in...were you able to try writing the returned properties to the log to find how to parse them?\n\nTo just count them, this seems to work by converting them to text and then splitting.\n\n* action: create variable\n * name: varIssueProperties\n * smart value: {{issue.properties}}\n* action: write to the log\n * the count is: {{varIssueProperties.split(\", \").size\\|0}}\n\nThanks!\n" } ] } ]

[ "json", "property", "smart-value" ]

[ { "author": "Andrej191", "body": "Solved via REST API. The problematic field was the custom field \"cascading select\". I do not think there is a way to set it using the Atlassian SDK, but the REST API can be used as a workaround.\n", "comments": [ { "author": "Bill Sheboy", "body": "Hi [@Andrej191](/t5/user/viewprofilepage/user-id/5566420) -- Welcome to the Atlassian Community!\n\nAs you solved your own question, do you want to mark this one as \"answered\"? That will help others in the community with similar needs find solutions faster. Thanks!\n\nKind regards, \nBill\n" } ] } ]

[ "cloud" ]

[ { "author": "Bill Sheboy", "body": "Hi [@Gilad Waldman](/t5/user/viewprofilepage/user-id/5405912)\n\nWhat are some examples of the contents of your customfield_10193? That may help to decide when / how to perform the replacement of spacing to underscores.\n\nFor example, some possible configurations might be:\n\n1. Alice *(Single value, with no delimiter)*\n2. Alice Jones *(Single value with first and last name, and no delimiter)*\n3. Alice Jones, Bob Smith, Eve *(Multiple names with a comma-space delimiter)*\n4. Alice Jones,Bob Smith,Eve *(Multiple names with a comma delimiter)*\n5. etc.\n\nFrom what you describe, I suspect it is a variation of #3, where the delimiter between names is a comma followed by a space.\n\nIn that case, you could try:\n\n* change the source so the delimiter is only a comma\n* replace the delimiter first in the advanced branch source, such as with:\n\n```\n{{issue.customfield_10193.split(\", \").join(\",\").replace(\" \",\"_\").split(\",\")}}\n```\n\nKind regards, \nBill\n", "comments": [ { "author": "Gilad Waldman", "body": "Thank you very much [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)\n\nYou are correct, my source is similar to #3 and looks like it works with new branch source.\n\nThanks!\n" } ] } ]

[ { "author": "Jack Brickey", "body": "Hi [@francis](/t5/user/viewprofilepage/user-id/781580) , you can certainly assign round-robin with JSM but I don't believe that is available in Jira. Assuming you are using JSM I would approach as follows.\n\n* trigger - issue created\n* condition - if/else for each time slot\n* action inside each if/else Assign using round robin based on a \"time zone support group\"\n\n![IMG_4451.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/341109i33A0D6B1EE3AE969/image-size/large?v=v2&px=999 \"IMG_4451.jpeg\")\n", "comments": [ { "author": "Bill Sheboy", "body": "Hi [@francis](/t5/user/viewprofilepage/user-id/781580)\n\nAdding to Jack's suggestion...\n\nMy understanding is when automation rules use round-robin (or balanced) assignment, that is tracked *at the level of a specific rule* . And so if a single rule uses conditional logic to select users from different groups, the assignment is unlikely to be balanced as expected. *(If an Atlassian team member knows differently, please respond with more information. Thanks!)*\n\nI suspect JSM has features to handle this situation, regardless of rule, Issue Assign Action behavior.\n\nWithout JSM, one rule workaround for this would be to create multiple rules, which check the condition for assignment. Then the round-robin will be tracked by each rule. And so for your scenario, you may need 5 rules, and the workload will be round-robin for the users assigned for each group used.\n\nKind regards, \nBill\n" }, { "author": "francis", "body": "Thanks all.\n\nThe fact that we can use the on-call roster in the assignment logic is a huge win. With the 'Balanced Workload' approach, the group of users is static and issues might be assigned to users who are not available. \n\n<br />\n\nI will have a look at the Smart Assignment app that [@Dave Rosenlund _Trundl_](/t5/user/viewprofilepage/user-id/1164057) suggested.\n" } ] }, { "author": "Dave Rosenlund _Trundl_", "body": "Hi, [@francis](/t5/user/viewprofilepage/user-id/781580) ? I hope you're well.\n\nI agree with [@Jack Brickey](/t5/user/viewprofilepage/user-id/853369)'s response. However, there are a couple of marketplace apps that you may wish to explore.\n\n[https://marketplace.atlassian.com/search?hosting=cloud\\&product=jira-service-management\\&query=Rotations](https://marketplace.atlassian.com/search?hosting=cloud&product=jira-service-management&query=Rotations)\n\nFull disclosure: I work for the company that makes one of the apps in the search results. \n\n-dave\n", "comments": null } ]

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

[ { "author": "Bill Sheboy", "body": "Hi [@Cedric Bridger](/t5/user/viewprofilepage/user-id/5564312) -- Welcome to the Atlassian Community!\n\nAnswering your last question first: there are probably alternatives in the Atlassian Marketplace to the built-in automation rules, or you could build your own application to make such changes using the REST API endpoints, or you could make the changes in a spreadsheet and import to update the dates, etc.\n\nBack to the original question...\n\nScenarios like this are problematic for automation rules as we are trying to implement features like cascading / recursive / bi-directional date changes (from project management tools), and so processing can quickly hit the automation service limits. One possible solution is to pick a date-change, direction (forward or backward), and remove the recursion.\n\nLet's confirm that **both of those rules** do not have the *allow rule trigger* option enabled. If they do, this is a unsolvable, rule deadlock condition. Please change so only one rule has the option enabled, or better still...\n\nAssuming only one rule has the option enabled (e.g., the downstream one triggered on the change to Due Date), one approach is:\n\n* disable the allow rule option completely for these rules;\n* for the rule triggered on Start Date change, add the additional logic to also edit the Due Date;\n* this will eliminate the looping, and only be limited by the 100 issues per branch in a rule; and\n* one cost of this change is replicating some logic between rules. (This is assuming the stand-alone rule triggered on change to Due Date is still needed.)\n\nKind regards, \nBill\n", "comments": [ { "author": "Cedric Bridger", "body": "Morning Bill,\n\nThanks for the help. I have so far integrated the 2 rules together, but as the automation on task A triggers the same automation on task B (As it edits the start date of linked task B) I still get a max-10 loop error. Attached is my new automation diagram\n\n![Screenshot 2024-08-09 103400.png](https://community.atlassian.com/t5/image/serverpage/image-id/340995i82E64706F0777221/image-dimensions/426x868?v=v2 \"Screenshot 2024-08-09 103400.png\")\n\nCould you advise if there is any way to avoid this loop error? I may have misunderstood your comment.\n" }, { "author": "Bill Sheboy", "body": "Did you **disable the option** in the rules' details (at the top) for this:\n> Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.\n" }, { "author": "Cedric Bridger", "body": "Hi Bill, disabling the option means the automation would not continue for the ongoing tasks.\n\nThe way I see it working is;\n\nChanging the start date for Task A auto adjusts the end date for task A based on a given no. of days listed as a Jira Smartvalue. The code also changes the start date for Task B to be the same as the new end date for Task A.\n\nAs task B's start date has been changed, the automation restarts and adjusts Task B's end date based on the corresponding no. of days listed in the task B Smart Value. It also adjusts the start date for Task C to be the same as the end date for task B.\n\nThe code reloops again, changing the end date for task C and the start date for task D ect.\n" }, { "author": "Bill Sheboy", "body": "As I first noted, recursive rules like this are unlikely to succeed and stay under the service limits unless there are a very small number of issues and they are used infrequently.\n\nWorse still, just one rule (or issue linkage) error could lead to using all rule capacity, shutting down execution for 12 to 24 hours on your site's automation. That could impact all of your co-workers' rule usage.\n\nRather than using automation rules, you may want to investigate the Advanced Planning features of higher Jira license levels or marketplace apps to solve this.\n" } ] } ]

[ { "author": "Marc - Devoteam", "body": "Hi [@M?lanie Liguet](/t5/user/viewprofilepage/user-id/4533707)\n\nWhat information is logged in the variable, are this multiple options?\n\nIf they are do an advanced branch in the rule based on the variable, then send the web request and edit action in the branch.\n", "comments": null }, { "author": "Bill Sheboy", "body": "Hi [@M?lanie Liguet](/t5/user/viewprofilepage/user-id/4533707)\n\n*First thing, I am not currently using JSM and so my suggestions are based on what I know about automation rules, in general. With that out of the way...*\n\nYou seem to be using this endpoint for getting the answers in the simplified format: <https://developer.atlassian.com/cloud/forms/rest/api-group-forms-on-issue/#api-issue-issueidorkey-form-formid-format-answers-get>\n\nThat one seems to indicate looping over the body, but you show what appears to be lists of labels and answers separated within the body.\n\nIs that what you see if you write the entire {{webhookResponse.body}} to the audit log?\n\nNext, what are you trying to do with the information as you iterate over it?\n\nKind regards, \nBill\n", "comments": [ { "author": "M?lanie Liguet", "body": "Hi,\n\nYes i use this apir rest.I I call it to have only the customers' responses rather than the entire form. \nI retrieve the question webhookResponse.body.label and the response webhookResponse.body.answer.\n\nThe goal is to allow the support team to be more responsive by directly displaying the information they need\n\nthe api does not allow to have the number of results returned\n\nI don't use {{webhookResponse.body}} because it is not formatted and therefore not very readable and I have useless information for the team such as the id or the choice\n\nregards\n" }, { "author": "Bill Sheboy", "body": "If you try writing {{webhookResponse.body}} *to the audit log when the rule runs*, it may indicate how to iterate over the values, producing something more useful for the team.\n" }, { "author": "Bill Sheboy", "body": "Hi [@M?lanie Liguet](/t5/user/viewprofilepage/user-id/4533707)\n\nI wanted to follow-up to learn if you had tried other parsing options yet. Perhaps something like this:\n\n```\n{{#webhookResponse.body}}\n* label: {{label}} with an answer: {{answer}}\n{{/}}\n```\n\nThanks!\n" } ] } ]

[ { "author": "Trudy Claspill", "body": "Hello [@sreenivasulu gundagula](/t5/user/viewprofilepage/user-id/5562680)\n\nWelcome to the Atlassian community.\n\nConditional display of fields based on other fields is not something that can be managed with Automation Rules.\n\nFor that you need a third party app. One app that might help you, depending on other factors of your scenario, is Behaviours for ScriptRunner.\n\n[https://marketplace.atlassian.com/apps/1228522/behaviours-scriptrunner-for-jira-cloud?tab=overview\\&hosting=cloud](https://marketplace.atlassian.com/apps/1228522/behaviours-scriptrunner-for-jira-cloud?tab=overview&hosting=cloud)\n", "comments": null } ]

[ { "author": "Bhanu", "body": "Hi [@Rania Haddadin](/t5/user/viewprofilepage/user-id/4251567)\n\nYou can try something like this:\n\nTrigger: Field Value Changed\n\nCondition: Jql to check if the issue vbelongs to the openSpring (Example: Project = JIRA and sprint not in openSprints()) \n\nAction: Transition Issue\n\nHope this helps!\n", "comments": [ { "author": "Rania Haddadin", "body": "It worked, thank you so much\n" } ] }, { "author": "Bill Sheboy", "body": "Hi [@Rania Haddadin](/t5/user/viewprofilepage/user-id/4251567)\n\nThere are two steps to building a rule like this:\n\n1. confirm the issue was in the open / active sprint\n2. confirm the issue is no longer in the open / active sprint\n\nThe first part is required to prevent updating issues which are modified in the backlog, and not in the current sprint. It may be done by either using the changelog fields to check the prior sprint values, or to initially \"mark\" (e.g., with a Label value) all issues in the sprint using another rule, triggered on Sprint Started...then check that \"mark\" before transitioning issues.\n\nThe second part may be checked with a JQL condition of sprint NOT IN openSprints().\n\nKind regards, \nBill\n", "comments": null } ]

[ { "author": "Bill Sheboy", "body": "Hi [@Shasheekant Patel](/t5/user/viewprofilepage/user-id/5371875)\n\nWhat is the symptom the other person is seeing that leads them to believe the label \"Subtask_Tree\" is not available.\n\nLabels are shown / recommended in the field after they are first used. Has the label been used in your site yet?\n\nKind regards, \nBill\n", "comments": [ { "author": "Shasheekant Patel", "body": "Hi [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)\n\nThank you for your response. I'd like to inform you that these labels have been used in other testing projects in the same Jira instance by me (Admin).\n" }, { "author": "Bill Sheboy", "body": "I recall this symptom could occur if the user account did not have create / edit issue permission...although that seems unlikely for this case.\n\nThere was an defect a few years ago for this symptom, which was fixed by Atlassian: <https://jira.atlassian.com/browse/JRACLOUD-74103>\n\nI recommend working with your Jira Site Admin to submit a ticket to Atlassian Support for their help. When you hear back from them, please post what you learn to benefit the community. <https://support.atlassian.com/contact/#/>\n" }, { "author": "Bill Sheboy", "body": "Hi [@Shasheekant Patel](/t5/user/viewprofilepage/user-id/5371875)\n\nI am following up to learn if you checked with the Atlassian Support team for this issue.\n\nThanks, \nBill\n" } ] } ]

[ "label" ]

[ { "author": "Bill Sheboy", "body": "Hi [@mateus_oliveira](/t5/user/viewprofilepage/user-id/5372025)\n\nTo find the issues with one (or more) of the same values selected as the trigger issue, you could use JQL like this:\n\n```\nproject = yourProject\n AND yourSelectionField IN (value1, value2, etc.)\n ORDER BY Key ASC\n```\n\nTo obtain the values from the trigger issue for the IN expression, [use a list iterator](https://confluence.atlassian.com/automation/jira-smart-values-lists-993924868.html#Jirasmartvalueslists-examplesExamples) over the selected values:\n\n```\nproject = yourProject\n AND yourSelectionField IN (\n {{#triggerIssue.yourSelectionField.value}}\"{{.}}\"{{^last}}, {{/}}{{/}}\n )\n ORDER BY Key ASC\n```\n\nPlease verify the correct smart value for your field before trying this expression. You may do that with this how-to article: <https://confluence.atlassian.com/automation/find-the-smart-value-for-a-field-993924665.html>\n\nKind regards, \nBill\n", "comments": [ { "author": "mateus_oliveira", "body": "Hi [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)\n\nThank you so much for your help, as always! In the automation log, I can see it did iterate through the values of the trigger issue and brought them together. I assume that, despite having multiple values in what looks like a string, it's used by the automation as an array with multiple values, right..?\n\nBut now, for some reason, I can't pass the lookup size to the smart variable... Would you know what could be the problem? \n\n<br />\n\n![Jira Automation Values.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/340357iFFCC171DDBEC45E1/image-size/large?v=v2&px=999 \"Jira Automation Values.jpg\") \n\nI'm under the impression the lookup was successful (since the log passed through it), but maybe it's not saving the number of issues found - or maybe it did not find any issues, when I'm sure they exist..?\n\nYou'll see I tried both the field name and also the cf\\[id\\], but none of them worked - at least, not in the lookup side... any of them works fine to get the trigger Issue values.\n" }, { "author": "Bill Sheboy", "body": "Looking at the audit log, the JQL is not correct.\n\nIs your custom field cf\\[30902\\] a multiple-select option field?\n\nIf so, please try the IN syntax and not the CONTAINS \\~ one:\n\n```\nproject = BCC AND?cf[30902] IN (?{{#triggerIssue.Target Specialties.value}}\"{{.}}\"{{^last}}, {{/}}{{/}} )\n```\n" }, { "author": "mateus_oliveira", "body": "Thank you Bill! \nI'm sorry, I haven't realized that the SQL needed adjustments in addition to the Smart Values iteration. But now, that worked flawlessly!\n\nThis took care of my most essential needs. Before finishing, would you know if it's possible to get the info of WHAT \"Target Specialties\" value had the most occurrences, or what had more than X occurrences?? I guess this would not be possible to do on the same lookup issues step, but is there any alternative? This would just be a plus, though.\n\nAnyway, once again, thanks! You saved our team operation.\n" }, { "author": "Bill Sheboy", "body": "Getting the maximum occurrences of specific values in a multiple-select field, or the count over a threshold, would be challenging with an automation rule.\n\nWith the current features of rules, I believe this could be done by saving the counts for each possible value and then using a series of comparisons. There may be other approaches using entity properties that are repeatedly updated, but that sounds like a brittle solution to me.\n" }, { "author": "mateus_oliveira", "body": "I would ask how to achieve the first option, saving the counts for each possible value and then comparing, but I believe the value would have to be stored in a created variable, right? And thus, that means the comparison/testing could not be dynamic anymore, right?\n\nConsidering that the number of values selected is completely different in every issue created, in the best scenario the variables to save the counts would also have to be created dynamically, which I don't think is possible without any plugins... so, to make this work, I believe I would have to create an IF/Else block for every possible value in the list, selected or not in any issue... That would require too much work, specially to maintain.\n\nThe solution we have right now solves the most urgent problem, so that'll be enough for now.\n\nOnce again, thank you Bill!\n" } ] }, { "author": "Adolfo Casari", "body": "[@mateus_oliveira](/t5/user/viewprofilepage/user-id/5372025) Should be cf\\[30902\\] IN (\"a\", \"b\", \"c\" ) , not \\~ \"a\", \"b\", \"c\"\n", "comments": null } ]

[ "jira-data-center", "jira-server", "jql", "select-list" ]

[ { "author": "Marc - Devoteam", "body": "Hi [@Josh Rossman](/t5/user/viewprofilepage/user-id/5519525)\n\nWhat is the config of the asset field.\n\nWhat are the values that you can get in a normal issue on the custom field of asset type?\n", "comments": [ { "author": "Josh Rossman", "body": "Marc,\n\nI was actually able to solve this by using name = {{alert.extraProperties.entity}}.\n\nAlthough my entity field within details was populated the Assets custom field would not reference it correctly. Since the entity field within Details does not show up within an alert by default you need to add it to extraProperties as well (referenced below.)\n\n<https://jira.atlassian.com/browse/JSDCLOUD-14561>\n\nI think this is the reason the assets field was unable to reference {{alert.entity}}.\n\nThanks!\n\nJosh R.\n" } ] }, { "author": "Adolfo Casari", "body": "[@Josh Rossman](/t5/user/viewprofilepage/user-id/5519525)If name = \"{{alert.entity}}\" don't work (but name = \"hostname\" does) can only mean that {{alert.entity}} don't hold a valid Linked Device name.\n\nHow do you configure that entity property for your alerts?\n", "comments": [ { "author": "Josh Rossman", "body": "The entity property is sent in the payload from our monitoring tools. For example, I was able to display the hostname via {{alert.entity}} in the description of an Issue. I know that part is pulling the hostname correctly. As soon as I try to place it within the Linked Device (Asset Object) field it's always left blank.\n" } ] } ]

[ "cloud" ]

[ { "author": "Matthias Gaiser _K15t_", "body": "[@Mitch Turner](/t5/user/viewprofilepage/user-id/5560582) I understood that the suggested solution is not fitting to you and you rather want to have a solution for issue links. If you scroll further down the list of **Type of related issues** , you will also find Linked Issues where you can also filter for the **Link types.**\n\nIn this branch, you can then again perform any action you want on that linked issue.\n\nThis example adds a comment for every issue which is linked with the type **clones**:\n\n![Screenshot 2024-08-06 at 07.56.55.png](https://community.atlassian.com/t5/image/serverpage/image-id/340162i53ECC522A22725DB/image-size/large?v=v2&px=999 \"Screenshot 2024-08-06 at 07.56.55.png\")\n\nIs that more helpful?\n", "comments": null }, { "author": "Matthias Gaiser _K15t_", "body": "Hey [@Mitch Turner](/t5/user/viewprofilepage/user-id/5560582)\n\nwelcome to the Atlassian Community.\n\nCan you please add some more details, e.g. a screenshot with the relevant sections how you've configured that so far?\n\nI'd go ahead and select the **Branch rule / related issues** action and select **Parent** as type of related issues.\n\nIf you perform actions below that branch, these will perform on the parent issue. See this example screenshot:\n\n![Screenshot 2024-08-05 at 08.47.22.png](https://community.atlassian.com/t5/image/serverpage/image-id/339939i46954B40D9640A02/image-size/large?v=v2&px=999 \"Screenshot 2024-08-05 at 08.47.22.png\")\n\nCheers, \nMatthias.\n", "comments": [ { "author": "Mitch Turner", "body": "All of the 'Parent' functions can't be used for the following reasons: \n\n1) JIRA cloud deprecated 'Epic Link' in favour of 'Parent Link' \nAll of the Standard automation 'Parent' Processing now uses the old 'Epic Link' field value for processing. So if its not defined as the 'Parent Link' via the old Epic Link function - its not picked up by any 'Parent' processing functions. \n\nThis also means that now the Parent issue MUST be of a certain issue type to qualify for 'Parent' - In my Case - both Parent and Child are the same issue type - meaning I can't use 'Parent Link' (Epic Link) to denote a Parent/child relationship. \n\nIm my particular circumstance -the Parent exists in another project - again - beside the point \n\n![parent_link_restrictions.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/340137i8C60851990681E31/image-size/large?v=v2&px=999 \"parent_link_restrictions.jpg\") \n\nIn JIRA cloud - there are now essentially two types of Parent linking. \n1) New \"Epic Link' type of Parent \n(which enforces issue type restrictions - must be an epic/story etc)\n\n2) Existing 'Linked Issue' type of Parent \n\nSo - unless the Parent is defined using the 'Parent Link' (Epic LInk) field - it won't be picked up by any of the 'Parent' automation functions like you have shown above. \n\nanyways - this is all beside trhe point. \n\nYou can still make a 'Parent Link' without using the old 'Epic Link' function. \nYou can do this via the 'Linked Issue' function like a 'is blocked by/depends on/ child of/Parent of etc.\n\nDon't get hung up on the 'Parent' processing. \n\nI probably should have asked how to comment on a Linked Issue\n\nSo my question essentially extends to making a comment or doing processing on any of those issues found as 'Linked Issues' \n\nI think the issue is in defining the 'for each' process. as cloud is not as flexible. \n\nI can identify and find the ID of related issues \nBut there's a simple problem with my the loop, as its posting a comment on the trigger issue and not the related issue. ... \n\nI'm pretty sure the cloud 'for each related issue' processing can;t be used - as it only has the following limited list of options, and none of these could be used to comment on any related issues aside from those types listed. \n\nunless of course I am missing something simple on how to use this.... \n\n![options.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/340131iB804A274F1E4A1E5/image-size/large?v=v2&px=999 \"options.jpg\") \n\n<br />\n" }, { "author": "Mitch Turner", "body": "I guess this question boils down to: \n\n\"How do you use JIRA Cloud Automation to process Linked issues\" \n\nand I think the answer may be \n\"You can't - because there is no for loop available for linked issues except those specified\"\n" }, { "author": "Mitch Turner", "body": "This also doesn't work if you use 'Child' as link type and the Child for the branch type. \n\nI guess it's computing Child based on Parent rather than the specific child link relationship being set, and also is using Parent Field (epic link) rather than Parent as a Link type.\n" } ] } ]

[ { "author": "Hans Polder", "body": "Hi [@Michael de Jonge](/t5/user/viewprofilepage/user-id/5558147) ,\n\nWelcome to the community!\n\nThere are two errors in your automation rule:\n\n1. You've defined 'lookupissues.size' but it should be 'lookupIssues.size' \\> it at least mattered in my test setup :)\n2. You cannot use 'smart values' directly in a JQL. You need to define it as a variable first.\n\nTIP: Use Log actions in your automation rule to see where it's failing.\n\nBelow automation works for me:\n\n![Screenshot 2024-08-01 105427.png](https://community.atlassian.com/t5/image/serverpage/image-id/339368i8BDC0ED41ECA8C8F/image-size/large?v=v2&px=999 \"Screenshot 2024-08-01 105427.png\")\n\nPS: The log actions are of course not needed once the rule is working fine, you should either leave them out, or remove them once the rule is working correctly.\n", "comments": [ { "author": "Hans Polder", "body": "PPS: I assume that you're either deleting the out of office tickets, or making them 'unassigned' after the person has returned from out of office \\> otherwise the script will always work for any past ticket as well. Or you should add some JQL logic like 'and status != Returned' to avoid past OoO's to be activating the rule.\n" }, { "author": "Michael de Jonge", "body": "Hi Hans, thanks for you clear explanation. I already fixed the assignee wich was a problem of adding \"\" around the {{}}.\n\nAnd thanks for the capital I in lookupIssues, that also solved a problem.\n\nSomehow i didn't need to add all the smart values and I AM able use them directly.\n\nThe working script for now:\n\n![Naamloos.png](https://community.atlassian.com/t5/image/serverpage/image-id/339370iE39CAE6F177AF3B2/image-size/large?v=v2&px=999 \"Naamloos.png\")\n\nThanks again for you help!\n" }, { "author": "Hans Polder", "body": "Ah, cool! I learned something new today :)\n\nOf course, all the 'add to audit log' entries were not needed, but good to know that you actually don't need to create the variable and just add the \"\" to make it work!\n" } ] } ]

[ { "author": "Theodora Boudale", "body": "Hi Appu and welcome to the community!\n\nThe **Downloads** section of a Bitbucket repository is not a package registry, so I'm not sure if it's possible to to download a file from there with the **pip install** command.\n\nYou can download the file using our API, but the credentials need to be provided separately and not as part of the URL. An example of such an API call with curl is the following:\n\n```\ncurl -s -L -O -u username:app_password https://api.bitbucket.org/2.0/repositories/workspace-id/repo-slug/downloads/my_package-0.1.0-py3-none-any.whl\n```\n\nwhere **username** , **app_password** , **workspace-id** and **repo-slug** replace with your own values. Also, replace **my_package-0.1.0-py3-none-any.whl** if the name of your package is different.\n\nReference:\n\n* <https://confluence.atlassian.com/bbkb/download-a-file-from-the-downloads-section-of-a-repository-1252006688.html>\n\nDoes this work for you?\n\nKind regards, \nTheodora\n", "comments": null } ]

[ "bitbucket-cloud", "cloud", "download", "pip" ]

[ { "author": "Theodora Boudale", "body": "Hi and welcome to the community!\n\nHow large are the files you are trying to push? I've seen this error occurs mainly with large pushes.\n\nYou can try increasing the size of the buffer used to POST data by executing the following command on a terminal application:\n\n```\ngit config --global http.postBuffer 157286400\n```\n\nThen, attempt to push again. This will increase the size of the buffer to 150 MB.\n\nAre you able to push then?\n\nKind regards, \nTheodora\n", "comments": [ { "author": "swelleye-brent", "body": "Hi Theodora, many thanks for your reply and help. That indeed fixed the issue! \n\nIt's strange because we've never had a limit on file size. We did recently upgrade our AWS instances, so perhaps the new instances had a limit. \n\nAnyway, thanks again for your help.\n" }, { "author": "Theodora Boudale", "body": "Hi,\n\nThank you for the update!\n\nI believe the default size of that buffer in Git is 1 MB, which may not be enough for larger pushes.\n\nIt's good to hear that this worked, please feel free to reach out if you ever need anything else!\n\nKind regards, \nTheodora\n" } ] } ]

[ "bitbucket-cloud", "cloud", "sourcetree" ]

[ { "author": "Theodora Boudale", "body": "Hi Priya and welcome to the community!\n\nThere is a bug preventing the removal of reviewers who have requested changed in the PR:\n\n* <https://jira.atlassian.com/browse/BCLOUD-21506>\n\nThe only way this reviewer can be removed is if they remove the 'requested changes' status. The reviewer will need to:\n\n1. Log in to <https://bitbucket.org/>\n2. Open the PR on Bitbucket's website\n3. Select the **Changes requested** option in the PR to remove the status: \n\n ![Screenshot 2024-09-20 at 12.09.41.png](https://community.atlassian.com/t5/image/serverpage/image-id/348366i2D69B2EFD88183E5/image-size/large?v=v2&px=999 \"Screenshot 2024-09-20 at 12.09.41.png\")\n\nYou will then be able to remove them from the PR's reviewers.\n\nPlease feel free to reach out if you have any questions!\n\nKind regards, \nTheodora\n", "comments": [ { "author": "Priya Iyer", "body": "Thanks, Theodora for the response.\n\nWhat if we are in a situation that reviewer had requested changes and say quit the job?\n\nHow do we go about this situation?\n\nFor Jira, we do get a option of rejecting a Peer review and one will assign a new reviewer mentioning it in audit trail that the earlier reviewer no longer works.\n\nIs there any Super user or Admin privileges that can help?\n" }, { "author": "Theodora Boudale", "body": "Hi Priya,\n\nI'm afraid that it is not possible to remove the status on behalf of another user even for admins. There isn't a super user role that can do that.\n\nUntil the bug is fixed, the options are:\n\n* The reviewer removes the status themselves. \n\n* For someone that quits the job, you can work with your IT department to get access to the user's email address, so you can reset the password for their Bitbucket account, log in to Bitbucket with the user's credentials and remove the status. \n\n* Decline the PR and create a new one. Please note that any comments, reviews, approvals made on the declined PR won't get transferred to the new one.\n\nKind regards, \nTheodora\n" } ] } ]

[ "bitbucket-cloud", "cloud" ]

[ { "author": "Patrik S", "body": "Hello [@P?mela Machado](/t5/user/viewprofilepage/user-id/5595721) ,\n\nand welcome to the Community!\n\nChecking internally I see that the bitbucket account associated with the email you posted this question from is already a member of a workspace, so hopefully the email eventually arrived. I also don't see any emails being bounced on our end, which usually suggest the email was delivered but may have been ended up on Spam/Junk folder on mistake.\n\nHowever, if the invitation is for a different account/email, we kindly ask you to post a comment here while logged in with the affected account email, so we can check our logs further.\n\nThank you, [@P?mela Machado](/t5/user/viewprofilepage/user-id/5595721) !\n\nPatrik S\n", "comments": null } ]

[ "bitbucket-cloud", "cloud", "invite" ]

[ { "author": "Patrik S", "body": "Hey [@Ka](/t5/user/viewprofilepage/user-id/5595715) ,\n\nwelcome to Community!\n\nYour Bitbucket Cloud account was put into an inactive state due to the long period with no login/activity.\n\nI went ahead and re-enabled the account, so you can log in as usual :)\n\nLet us know in case you are still having trouble signing in.\n\nThank you, [@Ka](/t5/user/viewprofilepage/user-id/5595715) !\n\nPatrik S\n", "comments": null }, { "author": "vikram", "body": "Hi [@Ka](/t5/user/viewprofilepage/user-id/5595715)\n\nWelcome to Atlassian Community.\n\nYes, your understanding is right, if you don't login to Bitbucket for long time, the account will be deactivated and you have to wait till it is activated from Atlassian people. --- Good luck.\n\nVikram P\n", "comments": null } ]

[ "bitbucket-cloud", "cloud" ]

[ { "author": "Patrik S", "body": "Hey [@Rashmitha Ramaraju](/t5/user/viewprofilepage/user-id/5591681) ,\n\nand welcome to the Community!\n\nI see you have opened an internal support ticket for this issue, so I would suggest focusing on the support ticket to avoid any confusions that may arise from discussing the same issue in multiple places.\n\nOnce the ticket is resolved, feel free to share the solution here in Community to help other users that may come across the same issue\n\nThank you, [@Rashmitha Ramaraju](/t5/user/viewprofilepage/user-id/5591681) ! :)\n", "comments": null } ]

[ "bitbucket-cloud", "cloud" ]

[ { "author": "Patrik S", "body": "Hey [@Dhanush P S](/t5/user/viewprofilepage/user-id/5595453) ,\n\nand welcome to the Community!\n\nUnfortunately, the selection of different viewers is only currently available in the Source tab.\n\nThe Commits tab will show the raw diff of changes introduced by that commit. It's the same as executing a ***git diff*** command locally, so it does not render the content of the file based on it's format, but rather prints the raw plain text content.\n\nThank you, [@Dhanush P S](/t5/user/viewprofilepage/user-id/5595453) !\n\nPatrik S\n", "comments": null } ]

[ "bitbucket-cloud", "cloud" ]

[ { "author": "Patrik S", "body": "Hey [@kwesiaryee](/t5/user/viewprofilepage/user-id/3242517) ,\n\nLooks like you have posted similar questions before:\n\n* [My VPS is not allowing port 22](https://community.atlassian.com/t5/Bitbucket-questions/My-VPS-is-not-allowing-port-22/qaq-p/2814024)\n\nI have added a suggestion that in that previous questions that if you're making use of the [atlassian/scp-deploy](https://bitbucket.org/product/features/pipelines/integrations?search=scp-&p=atlassian/scp-deploy) pipe to make your deployment, you may have it not correctly setup for the custom port.\n\nTo define a custom part when using the [atlassian/scp-deploy](https://bitbucket.org/product/features/pipelines/integrations?search=scp-&p=atlassian/scp-deploy) pipe, you'll need to set the EXTRA_ARGS variable, as in the following example:\n\n```\nscript:\n - pipe: atlassian/scp-deploy:1.5.1\n variables:\n USER: 'ec2-user'\n SERVER: '127.0.0.1'\n REMOTE_PATH: '/var/www/build/'\n LOCAL_PATH: 'build/'\n DEBUG: 'true'\n EXTRA_ARGS: [\"-P\", \"1035\"]\n```\n\nThank you, [@kwesiaryee](/t5/user/viewprofilepage/user-id/3242517) ! \nPatrik S\n", "comments": null } ]

[ "bitbucket-cloud", "cloud" ]

[ { "author": "Patrik S", "body": "Hello [@Doris Pusch](/t5/user/viewprofilepage/user-id/5595351) ,\n\nand welcome to the Community!\n\nYou should be able to start the reset of your two-factor authentication through the login screen by selecting the option **Forgot Code**.\n\nIt's important to note that you can enable 2FA at your atlassian account level, and also at the bitbucket account, so you may have more than one layer of 2FA enabled. For instructions on how to identify which is the layer and steps to reset it, the following article might be useful:\n\n* [How to Disable/Reset 2FA on Bitbucket Cloud and Atlassian Account](https://confluence.atlassian.com/bbkb/how-to-disable-reset-2fa-on-bitbucket-cloud-and-atlassian-account-1236932929.html)\n\nThank you, [@Doris Pusch](/t5/user/viewprofilepage/user-id/5595351) !\n\nPatrik S\n", "comments": null } ]

[ "bitbucket-cloud" ]

[ { "author": "Patrik S", "body": "Hey [@Mart? Bastida Comas](/t5/user/viewprofilepage/user-id/4658327) ,\n\nand thank you for reaching out to Community!\n\nWhen I spinned a container with the image that you shared, the following logs were printed right away:\n\n```\n$ docker run --rm -it espressif/idf:v4.4.7 /bin/bash\n\nDetecting the Python interpreter\nChecking \"python\" ...\nPython 3.8.10\n\"python\" has been detected\nAdding ESP-IDF tools to PATH...\nUsing Python interpreter in /opt/esp/python_env/idf4.4_py3.8_env/bin/python\nChecking if Python packages are up to date...\nPython requirements from /opt/esp/idf/requirements.txt are satisfied.\nAdded the following directories to PATH:\n /opt/esp/idf/components/esptool_py/esptool\n /opt/esp/idf/components/espcoredump\n /opt/esp/idf/components/partition_table\n /opt/esp/idf/components/app_update\n /opt/esp/tools/xtensa-esp-elf-gdb/11.2_20220823/xtensa-esp-elf-gdb/bin\n /opt/esp/tools/riscv32-esp-elf-gdb/11.2_20220823/riscv32-esp-elf-gdb/bin\n /opt/esp/tools/xtensa-esp32-elf/esp-2021r2-patch5-8.4.0/xtensa-esp32-elf/bin\n /opt/esp/tools/xtensa-esp32s2-elf/esp-2021r2-patch5-8.4.0/xtensa-esp32s2-elf/bin\n /opt/esp/tools/xtensa-esp32s3-elf/esp-2021r2-patch5-8.4.0/xtensa-esp32s3-elf/bin\n /opt/esp/tools/riscv32-esp-elf/esp-2021r2-patch5-8.4.0/riscv32-esp-elf/bin\n /opt/esp/tools/esp32ulp-elf/2.35_20220830/esp32ulp-elf/bin\n /opt/esp/tools/cmake/3.23.1/bin\n /opt/esp/tools/openocd-esp32/v0.12.0-esp32-20230921/openocd-esp32/bin\n /opt/esp/python_env/idf4.4_py3.8_env/bin\n /opt/esp/idf/tools\nDone! You can now compile ESP-IDF projects.\nGo to the project directory and run:\n idf.py build\n```\n\nThis means that your image has a command set as the entrypoint that executes as soon as the image is started, setting up the environment and adding the ESP-IDF tools to the PATH (PATH is where executables are looked for).\n\nWhat happens is that pipelines overwrites the image's entrypoint to /*bin/bash*, so pipelines can executed the script you have defined in the steps. This would be similar to starting the local container as follows:\n\n```\ndocker run --rm -it --entrypoint=/bin/bash espressif/idf:v4.4.7\n```\n\nSo the entrypoint you have configured in your image is actually skipped, and the container starts directly in a bash session.\n\nAs that entrypoint is apparently what is setting up the environment and setting the PATH to contain the IDF executable, skipping the entrypoint is causing the pipelines not being able to find that command idf.py in PATH.\n\nMy suggestion in this case would be to either:\n\n* Get the commands configured as the entrypoint in that public docker image, and manually add those commands as part of the first commands in your step's script\n* If you know the path to that executable *idf.py* inside the image, you can add that to the PATH variable :\n\n export PATH=$PATH:/<path to the executable>\n\nI hope that helps! Let us know in case you have any questions.\n\nThank you, [@Mart? Bastida Comas](/t5/user/viewprofilepage/user-id/4658327) !\n\nPatrik S\n", "comments": null } ]

[ "bitbucket-cloud", "bitbucket-pipelines", "cloud", "docker" ]

[ { "author": "M.Shimizu", "body": "??????????????????\n\n?????????????????????????????????????????????????????????????????\n\n[https://community.atlassian.com/t5/Bitbucket-discussions/This-is-a-large-pull-request-Large-pull-requests-can-only-be/m-p/2582796#M4431](https://community.atlassian.com/t5/Bitbucket-discussions/This-is-a-large-pull-request-Large-pull-requests-can-only-be/td-p/1419570)\n\n---\n\n* Reduce the zoom on your browser to 90%.\n* Reload the page.\n* Restore zoom to 100%\n\n---\n\n????????????????????????????????????????????????????\n\n<https://support.atlassian.com/ja/contact/#/>\n\n?????????????????\n", "comments": null }, { "author": "Patrik S", "body": "Hello [@????](/t5/user/viewprofilepage/user-id/5595056) ,\n\nand welcome to the Community!\n\nThat message is usually shown when you're reviewing a large pull request that includes a lot of changes and ends up exceeding the [Limits for viewing contents and diffs](http://Atlassian%20Support / Bitbucket / Resources / Set up and work on repositories in Bitbucket Cloud / Manage large files with Git Large File Storage (LFS) Cloud Data Center Limits for viewing content and diffs) :\n> * A file's diff cannot exceed 2000 changed lines or 102,400 bytes (100 KB) of raw diff data.\n>\n> * The entire diff cannot exceed 8000 changed lines.\n>\n> * The maximum number of files in a single diff is limited to *200*.\n\nCould you please confirm if the diff of your pull request is not exceeding any of those limits?\n\nThank you, [@????](/t5/user/viewprofilepage/user-id/5595056) !\n\nPatrik S\n", "comments": null }, { "author": "????", "body": "git diff????No Newline at End of File????????????????????\n\n????????????????????????????????\n", "comments": null } ]

[ "bitbucket-cloud", "cloud" ]

[ { "author": "Kseniia Trushnikova", "body": "Hi [@Dipen Pal](/t5/user/viewprofilepage/user-id/5595165),\n\nIt might be a permission issue. Check out this [question](https://stackoverflow.com/questions/42214667/what-does-git-mean-by-unable-to-migrate-objects-to-permanent-storage) and answers to it on stackoverflow.\n\nSome objects in the repo may be owned not by the user you're trying to push with. In this case, try the commands **chmod/chown** in this repo.\n", "comments": null } ]

[ "bitbucket-data-center", "data-center" ]

[ { "author": "Aron Gombas _Midori_", "body": "I think you should be able to access the Bitbucket Cloud REST API from a pipeline using \"curl\".\n\nJust send requests to the corresponding endpoints and you have the information in the API response. It should be fairly trivial.\n\nSee: <https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pipelines/#api-repositories-workspace-repo-slug-pipelines-pipeline-uuid-get>\n", "comments": null } ]

[ "bitbucket-cloud", "cloud" ]

[ { "author": "Syahrul", "body": "G'day, [@amreshprasad](/t5/user/viewprofilepage/user-id/5594627)\n\nWelcome to the community!\n\nI apologize for the delay. I have triggered GC on the affected repository, which is now 665 MB.\n\nI hope this helps\n\nRegards, \nSyahrul\n", "comments": null }, { "author": "Robert Wen_ReleaseTEAM_", "body": "Hello [@amreshprasad](/t5/user/viewprofilepage/user-id/5594627) ! Welcome to the Atlassian Community!\n\nI've summoned someone from Atlassian Support. They will see your issue from here on.\n", "comments": [ { "author": "amreshprasad", "body": "Any updates?\n" }, { "author": "Robert Wen_ReleaseTEAM_", "body": "It's 2 business days.\n" } ] } ]

[ "bitbucket-cloud", "cloud" ]

[ { "author": "Patrik S", "body": "Hey [@Bartosz Dobija](/t5/user/viewprofilepage/user-id/5594341) ,\n\nand welcome to the Community!\n\nI was able to reproduce this, so I'm checking this internally with our engineering team and will get back to you as soon as I have an update.\n", "comments": null } ]

[ "bitbucket-cloud", "breaking-change", "cloud", "next", "pagination" ]

[ { "author": "Patrik S", "body": "Hello [@vvlnv](/t5/user/viewprofilepage/user-id/5594283) ,\n\nand welcome to the Community!\n\nWe really appreciate your feedback, and we do have a feature request opened with our engineering team to make the Bitbucket page more responsible and improve usability on small screens:\n\n* <https://jira.atlassian.com/browse/BCLOUD-5795>\n\nI would recommend adding a comment in there with your suggestions and the things you're facing difficulties achieving with the current UI, so our product managers can better understand your use case and the demand for this feature.\n\nYou also have the option to add yourself as a watcher to that feature request, so you'll get notified of any future updates.\n\nThank you, [@vvlnv](/t5/user/viewprofilepage/user-id/5594283) !\n\nPatrik S\n", "comments": null } ]

[ "bitbucket-unknown-hosting-type", "design", "pull-request", "ui", "unknown-hosting-type" ]

[ { "author": "vikram", "body": "Hi [@kwesiaryee](/t5/user/viewprofilepage/user-id/3242517)\n\nWelcome to Atlassian Community.\n\nAs per your information your port is changed to 2013 as per secuirty.\n\nPlease use 2013 port instead of 22 as below\n\nssh: connect to host IP port 2013 and try.\n\nLet me know if it works.\n\nVikram P\n", "comments": [ { "author": "kwesiaryee", "body": "I've tried several times and the following is what i get:\n\nINFO: Starting SCP deployment to IP:2013:/home/directory/public_html/... \nscp -rp -i /opt/atlassian/pipelines/agent/ssh/id_rsa_tmp dist/spa/assets dist/spa/favicon.ico dist/spa/icons dist/spa/index.html root@IP:2013:/home/directory/public_html/ \nssh: connect to host IP port 22: Connection refused \nlost connection \n? Deployment failed. \naca9d7420f98: Pull complete \n0f3ac11eee9e: Pull complete \nDigest: sha256:92cc16bb0a383f038bdc2443d0ea83dc390aa2f19beb0f56bf3c77ffff78ef41 \nStatus: Downloaded newer image for bitbucketpipelines/scp-deploy:0.3.3 \nINFO: Starting SCP deployment to IP:2013:/home/directory/public_html/... \nscp -rp -i /opt/atlassian/pipelines/agent/ssh/id_rsa_tmp dist/spa/assets dist/spa/favicon.ico dist/spa/icons dist/spa/index.html root@IP:2013:/home/directory/public_html/ \nssh: connect to host IP port 22: Connection refused \nlost connection \n? Deployment failed.\n" }, { "author": "vikram", "body": "Hi [@kwesiaryee](/t5/user/viewprofilepage/user-id/3242517)\n\nThanks for update,\n\ncan you please try below commands to verify ssh server status:\n\nsystemctl status ssh ---- checks the status of the SSH service on systemd-based Linux system. \nservice ssh status ---- checks the status of the SSH service on a system. \nss -tln --- lists all listening TCP sockets on the system including SSH server's port. \nnetstat -tuln --- same as above but also lists active listening TCP sockets including SSH port. \nping \\<hostname or IP\\> ---- Test basic network connectivity to a remote host. \ntraceroute \\<hostname or IP\\> --- Traces the route packets to reach remote host.\n\nvikram P\n" } ] }, { "author": "Patrik S", "body": "Hey [@kwesiaryee](/t5/user/viewprofilepage/user-id/3242517) ,\n\nbased on the error message you shared, it seems you're using the [atlassian/scp-deploy](https://bitbucket.org/product/features/pipelines/integrations?search=scp-&p=atlassian/scp-deploy) pipe. Is that correct ?\n\nIf yes, then you need to define the custom port as part of the EXTRA_ARGS variable, as in the following example:\n\n```\nscript:\n - pipe: atlassian/scp-deploy:1.5.1\n variables:\n USER: 'ec2-user'\n SERVER: '127.0.0.1'\n REMOTE_PATH: '/var/www/build/'\n LOCAL_PATH: 'build/'\n DEBUG: 'true'\n EXTRA_ARGS: [\"-P\", \"2013\"]\n```\n\nThank you, [@kwesiaryee](/t5/user/viewprofilepage/user-id/3242517) !\n\nPatrik S\n", "comments": [ { "author": "kwesiaryee", "body": "The following is my pipeline:\n\n```\nmaster:\n\n - step:\n\ncaches:\n\n - node\n\ndeployment: Production\n\nscript: # Pushing to the master branch\n\n - apt-get update\n\n - apt-get install -y openssh-client rsync\n\n - npm i -g @quasar/cli\n\n - npm install\n\n - npm run lint\n\n - npm run format\n\n - quasar build\n\nartifacts:\n\n - dist/**\n\n - step:\n\nname: Deploy dist folder to server via SCP\n\nscript:\n\n - pipe: atlassian/scp-deploy:0.3.3\n\nvariables:\n\nUSER: $USER\n\nSERVER: $SERVER\n\nREMOTE_PATH: \"/home/directory/public_html/\"\n\nLOCAL_PATH: \"${BITBUCKET_CLONE_DIR}/dist/spa/*\"\n\nDEBUG: \"true\"\n\nEXTRA_ARGS: [\"-P\", \"2013\"]\n```\n\nThis is per your sample above, but I'm still getting an error as follows:\n\n```\nStatus: Downloaded newer image for bitbucketpipelines/scp-deploy:0.3.3\nDEBUG: Using default ssh key\nINFO: Starting SCP deployment to IP:2013:/home/directory/public_html/...\nscp -rp -i /opt/atlassian/pipelines/agent/ssh/id_rsa_tmp /opt/atlassian/pipelines/agent/build/dist/spa/assets /opt/atlassian/pipelines/agent/build/dist/spa/favicon.ico /opt/atlassian/pipelines/agent/build/dist/spa/icons /opt/atlassian/pipelines/agent/build/dist/spa/index.html root@IP:2013:/home/directory/public_html/\nssh: connect to host IP port 22: Connection refused\nlost connection\n? Deployment failed.\naca9d7420f98: Pull complete\n0f3ac11eee9e: Pull complete\nDigest: sha256:92cc16bb0a383f038bdc2443d0ea83dc390aa2f19beb0f56bf3c77ffff78ef41\nStatus: Downloaded newer image for bitbucketpipelines/scp-deploy:0.3.3\nDEBUG: Using default ssh key\nINFO: Starting SCP deployment to IP:2013:/home/directory/public_html/...\nscp -rp -i /opt/atlassian/pipelines/agent/ssh/id_rsa_tmp /opt/atlassian/pipelines/agent/build/dist/spa/assets /opt/atlassian/pipelines/agent/build/dist/spa/favicon.ico /opt/atlassian/pipelines/agent/build/dist/spa/icons /opt/atlassian/pipelines/agent/build/dist/spa/index.html root@IP:2013:/home/directory/public_html/\nssh: connect to host IP port 22: Connection refused\nlost connection\n? Deployment failed.\n```\n\nKwesi\n" }, { "author": "Patrik S", "body": "Hello [@kwesiaryee](/t5/user/viewprofilepage/user-id/3242517) ,\n\nIt looks like you're using a very old version of the pipe, that didn't yet support EXTRA_ARGS option, so that's the reason why it's not being taken into account.\n\nCould you please update your command to use the latest version instead (1.5.1) ?\n\n```\nscript:\n - pipe: atlassian/scp-deploy:1.5.1\n variables:\n USER: 'ec2-user'\n SERVER: '127.0.0.1'\n REMOTE_PATH: '/var/www/build/'\n LOCAL_PATH: 'build/'\n DEBUG: 'true'\n EXTRA_ARGS: [\"-P\", \"2013\"]\n```\n\nAlso, it's important to highlight that the port number needs only to be provided as the EXTRA_ARGS value. The SERVER variable should only contain the IP/domain of your server, not the port.\n" } ] }, { "author": "kwesiaryee", "body": "Hi Vikram,\n\nThanks a lot for your response.\n\nI got the following response from my terminal:\n\nnetstat -tuln: tcp 0 0 0.0.0.0:2013 0.0.0.0:\\* LISTEN\n\nservice ssh status: Unit ssh.service could not be found.\n\nservice ssh status \nRedirecting to /bin/systemctl status ssh.service \nUnit ssh.service could not be found. \n\nping \\<hostname or IP\\>: -bash: port: command not found\n\ntraceroute \\<hostname or IP\\> : command not found\n\nI am using almaLinux 9 as server os.\n\nKwesi\n", "comments": null } ]

[ "bitbucket-cloud", "cloud" ]

[ { "author": "Patrik S", "body": "Hey [@FanFataL](/t5/user/viewprofilepage/user-id/4237994) ,\n\nand welcome to the Community!\n\nCould you please clarify if the difference you noticed was in the background color, or in the font color ?\n\nI ask this because it may be the case that you have enabled syntax highlighting in your personal profile, which changes the rendering of the diff. If that is the case, you may want to try disabling Syntax Highlighting by navigating to the [Labs section of your Personal Bitbucket Settings](https://bitbucket.org/account/settings/features/).\n\nThank you, [@FanFataL](/t5/user/viewprofilepage/user-id/4237994) !\n\nPatrik S\n", "comments": [ { "author": "FanFataL", "body": "Yes, I'm using this. But the colors were changed to worst.\n\nThis is old highlight of vue/html syntax\n\n![image (12).png](https://community.atlassian.com/t5/image/serverpage/image-id/348252i883A0CC6FA47D8A2/image-size/large?v=v2&px=999 \"image (12).png\")\n\nAnd this is new:\n\n![Screenshot from 2024-09-19 21-45-29.png](https://community.atlassian.com/t5/image/serverpage/image-id/348253iC21A55C20232C74A/image-size/large?v=v2&px=999 \"Screenshot from 2024-09-19 21-45-29.png\")\n" }, { "author": "Patrik S", "body": "Hey [@FanFataL](/t5/user/viewprofilepage/user-id/4237994) ,\n\nthanks for the confirmation!\n\nIn that case, I would recommend sharing your feedback about the colors directly in the Labs feature, using the *Give feedback* button:\n\n![Screenshot 2024-09-19 at 6.06.06?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/348262iAB7B76D7C80173D2/image-size/large?v=v2&px=999 \"Screenshot 2024-09-19 at 6.06.06?PM.png\")\n\nSo your feedback will be directly shared with our product managers and engineering team responsible for that feature.\n\nThank you, [@FanFataL](/t5/user/viewprofilepage/user-id/4237994) !\n\nPatrik S\n" }, { "author": "FanFataL", "body": "Thanks\n" } ] } ]

[ "bitbucket-cloud", "cloud", "diff", "pull-request" ]

[ { "author": "Patrik S", "body": "Hello [@Peter Miller](/t5/user/viewprofilepage/user-id/5483170) ,\n\nand thanks for reaching out to the Community!\n\nWhen you click on a commit in the Pull Request Overview tab, the page will redirect you to the Files changed tab and filter the diff **to only that single commit**. This is the reason why you see less files changed, because the diff in this case is not considering all the commits in the pull request, but that single commit you have clicked.\n\nTo view the diff of all the commits, you can click on the dropdown and select All changes, like in the below example :\n\n![Screenshot 2024-09-19 at 2.09.51?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/348227i2AB24905BA6CB8B2/image-size/large?v=v2&px=999 \"Screenshot 2024-09-19 at 2.09.51?PM.png\")\n\nThat dropdown enables you to see the different across individual commits, or a range of commits you select. It also has the option to show All changes, which will make the diff considering all the commits that are part of that pull request.\n\nI hope that helps to clarify!\n\nThank you, [@Peter Miller](/t5/user/viewprofilepage/user-id/5483170) !\n\nPatrik S\n", "comments": [ { "author": "Peter Miller", "body": "ah that makes sense. thanks.\n\ni found the reason i'm seeing a commit from a different PR inside this PR is that the commit is a merge from the master branch into this branch\n" } ] } ]

[ "bitbucket-cloud", "cloud" ]

[ { "author": "vikram", "body": "Hi [@developerchan1](/t5/user/viewprofilepage/user-id/5594209)\n\nWelcome to Atlassian Community\n\nAs per the last update from bitbucket they suggested to force git to use IPV4 by adding following entry to /etc/hosts file:\n\n```\n104.192.143.2 bitbucket.org\n```\n\nand add the Google DNS servers to your network settings:\n\n![mac_os_config.png](https://community.atlassian.com/t5/image/serverpage/image-id/347724i006EF6A1E4E8EA48/image-size/large?v=v2&px=999 \"mac_os_config.png\")\n", "comments": [ { "author": "developerchan1", "body": "Hello Mr. [@vikram](/t5/user/viewprofilepage/user-id/5005662)\n\nFirst of all, thank you so much for your suggestion. After I tried your suggestion, it's still can't connect to bitbucket. However after I delete bitbucket.org from /etc/hosts, finally I can smoothly connect to bitbucket (both website or via git). Just for information, before you suggest to add/change ip address for bitbucket, there are already here with differ ip). \n\nThank you so much again for your resolution Mr [@vikram](/t5/user/viewprofilepage/user-id/5005662)\n" } ] } ]

[ "bitbucket-cloud", "cloud" ]

[ { "author": "Patrik S", "body": "Hello [@IRTSoft - Chef de Projet Web](/t5/user/viewprofilepage/user-id/5594189) ,\n\nand welcome to the Community!\n\nUnfortunately it's not possible to access an account without the email address, as the email is used to proof ownership. You'd need first to recover the email address to then login on Bitbucket Cloud.\n\nAs an alternative, as you mentioned you still have the credentials to clone/pull the repositories, you could clone all the repositories within that workspace and then push to a new workspace that you can create using your bitbucket account with the current email.\n\nI hope that helps! Let us know in case you have any questions.\n\nThank you, [@IRTSoft - Chef de Projet Web](/t5/user/viewprofilepage/user-id/5594189) !\n\nPatrik S\n", "comments": null } ]

[ "bitbucket-cloud", "cloud" ]

[ { "author": "Theodora Boudale", "body": "Hi [@gnedin](/t5/user/viewprofilepage/user-id/1814662) and welcome to the community!\n\nDid you push this commits to the repo's main branch, or a different one?\n\nYou can double-check which branch is the main one from **Repository settings** \\> **Repository details** \\> select **ADVANCED** and you'll see the **Main branch** listed there.\n\nThe sync button will show only if there are changes on the repo's main branch.\n\nKind regards, \nTheodora\n", "comments": null } ]

[ "bitbucket-cloud", "cloud" ]

[ { "author": "Mohammad", "body": "**Solution** This issue refers into proguard-rules if used inside the app in my case update this file and its work fine\n\nYou find missing's scripts inside mappings directories\n", "comments": null }, { "author": "Theodora Boudale", "body": "Hi Mohammad!\n\nI'm not familiar with flutter, so I can't answer any questions related to that. However, I can give you some context on the environment that Pipelines builds run so you can debug this.\n\nIf you run Pipelines builds on Atlassian's infrastructure or with a self-hosted Linux Docker runner, these builds run in Docker containers based on the Docker image you have specified in your bitbucket-pipelines.yml file.\n\nIf you have Docker installed on your computer, you can debug a Pipelines build locally with Docker following this guide:\n\n* <https://confluence.atlassian.com/bbkb/troubleshoot-failed-bitbucket-pipelines-locally-with-docker-1318882094.html>\n\nIf you follow the steps of the guide, you'll have a clone of the repo at the same commit as the failed build and also use the same Docker image.\n\nYou can then debug the issue locally without consuming Pipelines minutes and run additional commands to debug it.\n\nYou could also try different Docker images if the one you are using now does not have the version of the tools you need. We support public and private Docker images including those hosted on Docker Hub, AWS, GCP, Azure and self-hosted registries accessible on the internet:\n\n* <https://support.atlassian.com/bitbucket-cloud/docs/use-docker-images-as-build-environments/>\n\nIf you run Pipelines builds with a self-hosted Linux Shell, MacOS, or Windows runner, these builds run directly on the host machine using Bash (Linux Shell and MacOS runners) and PowerShell (Windows runners). You can debug these builds outside the runner using Bash or PowerShell respectively.\n\nPlease feel free to reach out if you have any questions!\n\nKind regards, \nTheodora\n", "comments": [ { "author": "Mohammad", "body": "Thx [@Theodora Boudale](/t5/user/viewprofilepage/user-id/818086) ??\n" }, { "author": "Theodora Boudale", "body": "You are very welcome! Thank you also for posting the solution!\n" } ] } ]

[ "bitbucket-cloud", "bitbucket-pipelines", "cloud", "dart", "developer", "devops", "flutter", "google", "jira" ]