Datasets:

---

clips

/

mqa

like 52

Follow

CLiPS 10

[ { "text": "[image]\n\n[allowing an app to use the trello api stopped working](https://community.developer.atlassian.com/t/allowing-an-app-to-use-the-trello-api-stopped-working/42709/9) [trello](/c/trello)\n\nboth <https://trello.com/1/client.js> and <https://trello.com/1/client-unminified.js> are back.\n\nthere were a few hours where client.js was not served from trello.com/1/, unfortunately. we are working on maki…", "name": "", "is_accepted": true } ]

[ { "text": "hi, we solved send the reporter by the velocity to the function with the next form\n\ngetmyoptions(\"$!{issue.reporter.name}\", \"$!{issue}\")\n\nalso on the js we can get the value on the form with this line:\n\nreporter = $(\"#reporter\").val()", "name": "", "is_accepted": true } ]

[ { "text": "[@karthikeyan](/u/karthikeyan),\n\nit looks like that’s pretty straight forward with get /rest/servicedeskapi/knowledgebase/article that [get articles](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-knowledgebase/). the payload returned is a list of articles with the right parts to know about confluence:\n\n{\n\n...\n\n\"values\": [\n\n{\n\n\"title\": \"stolen computer\",\n\n\"excerpt\":…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@miguel.ortigueira](/u/miguel.ortigueira) ,\n\nthe trello logo on atlassian.design is the one to use! the trello logo using the new atlassian logo style is only to be used when grouped with the rest of the logo family.\n\ncheers,\n\nlucy", "name": "", "is_accepted": true } ]

[ { "text": "as server side fix we use [custom context parameters](https://developer.atlassian.com/cloud/jira/platform/context-parameters/) however they are available for page modules only. for webpanels you could use some hack with ap.getlocation", "name": "", "is_accepted": true } ]

[ { "text": "hello [@muhammadusman](/u/muhammadusman)\n\nthere is no single answer, as there is always a ‘person’ involved, since authenticating to the rest api requires a user’s credentials. the only difference is that oauth is meant for applications that will present that user, a real person, with an interface to approve the applic…", "name": "", "is_accepted": true } ]

[ { "text": "almost. you’ll want to use the applicationlinkservice: <https://docs.atlassian.com/applinks-api/3.2/com/atlassian/applinks/api/applicationlinkservice.html>\n\nthen in it get the appropriate applicationlink (in your case i’m guessing that it’s going to be all of the jira instances - so look at [https://do…](https://docs.atlassian.com/applinks-api/3.2/com/atlassian/applinks/api/applicationlinkservice.html#getapplicationlinks(java.lang.class))", "name": "", "is_accepted": true } ]

[ { "text": "if anyone is interested, the solution is to set metadata.property editor to “v2”.\n\ni’ve done it in the success function of ap.request that creates a new page (post to /rest/api/content) since the response from that call includes the id of the newly created page. check out [create content property res…](https://developer.atlassian.com/cloud/confluence/rest/#api-api-content-id-property-post)", "name": "", "is_accepted": true } ]

[ { "text": "managed to solve this problem as following:\n\nthis error wont show up with local agents, but only with remote agents. so instead of testing using atlassian-sdk, i debugged it locally using bamboo server and agent docker images.\n\nthe issue is with the dependency applicationproperties, i wasnt using th…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@tonygoughadaptavist](/u/tonygoughadaptavist) ,\n\nthis seems like a regression from the legacy editor.\n\nlegacy editor:\n\n[[v1-editor]](https://aws1.discourse-cdn.com/atlassiandeveloper/original/3x/6/f/6f26beb4ea14e152253ad20cd7ad770540e32f98.png \"v1-editor\")\n\nnew editor:\n\n[[v2-editor]](https://aws1.discourse-cdn.com/atlassiandeveloper/original/3x/d/c/dc04dbd1a25f580433caf9ee716a56ec066caad2.png \"v2-editor\")\n\nif you want to reproduce this, install <https://dx-macro-icons-app.glitch.me/connect.json>. the code is [here](https://glitch.com/edit/#!/dx-macro-icons-app?path=connect.json%3a13%3a48).\n\nperhaps there’s a reason for this change in behaviour…", "name": "", "is_accepted": true } ]

[ { "text": "thanks for clarifying.\n\nwe’re working on it. it’ll show the custom field type.", "name": "", "is_accepted": true } ]

[ { "text": "i realized that i can pass current user id by url in secure way, because of qsh claim in jwt :slight\\_smile:", "name": "", "is_accepted": true } ]

[ { "text": "i would use multiple instances of ace: one for each atlassian app. this would mean that, should one app malfunction, the other will be unaffected. this is a desirable characteristic. i would also make it so that you keep the apps as separate as possible and, if they need to communicate or share data…", "name": "", "is_accepted": true } ]

[ { "text": "solved my issue! had to add this to the amps portion of the pom.xml:\n\n<extractdependencies>false</extractdependencies>", "name": "", "is_accepted": true } ]

[ { "text": "hi [@alexter\\_pr](/u/alexter_pr),\n\nit doesn’t look like this is documented at all, but atlassian-connect-express emits an event on successful installation: host\\_settings\\_saved. see [lib/index.js](https://bitbucket.org/atlassian/atlassian-connect-express/src/e8e6a7a70e06ef68b557e21046e35988d1141b24/lib/index.js?at=v2.1.3&fileviewer=file-view-default#index.js-148).", "name": "", "is_accepted": true } ]

[ { "text": "nevermind, didn’t realize that the sprint field is a custom field and is referred to as “customfield\\_{id}”", "name": "", "is_accepted": true } ]

[ { "text": "hi [@glib.briia](/u/glib.briia),\n\nno, i’m afraid that is not currently supported. the framework handles the installation callback for you, so i’m not sure how you would go about adding it. feel free to raise a feature request in [acspring](https://ecosystem.atlassian.net/browse/acspring).\n\ncheers,\n\neinar", "name": "", "is_accepted": true } ]

[ { "text": "just checked with the marketplace team to confirm. if you want the cloud version to be on the same listing as the server version (which i assume you do) then you definitely want to keep the same app key.", "name": "", "is_accepted": true } ]

[ { "text": "hello,\n\nthanks for your answer.\n\nthe command line option -dallow.google.tracking=false works fine for me.", "name": "", "is_accepted": true } ]

[ { "text": "hi [@acalantog](/u/acalantog),\n\nit is after. i was never able to access the velocity variable directly from the js web-resource but did work around by setting and getting meta data variables.\n\nhere’s a snippet:\n\nwebform.vm\n\n#putmetadata(\"submitdatemeta\", $webformmacroobject.getproperty(\"submitdate\"))\n\ncreateinitia…", "name": "", "is_accepted": true } ]

[ { "text": "as far as i see it is not suposed for doing dynamic stuff - register the validation stuff for the form exactly one time, submit the form, validation gets “lost” because of the rerendering…\n\nin order to “abuse” the functionality i did a quick an dirty workaround: each time the main select box changes…", "name": "", "is_accepted": true } ]

[ { "text": "try something like this:\n\npublic class foo implements initializingbean, disposablebean {\n\nprivate final eventpublisher eventpublisher;\n\npublic foo(eventpublisher eventpublisher) {\n\nthis.eventpublisher = eventpublisher;\n\n}\n\n/** called when the plugin has been enabled */\n\n@ove…", "name": "", "is_accepted": true } ]

[ { "text": "you should be able to do this using <https://www.npmjs.com/package/bitbucket> (api documentation can be found here: <https://bitbucketjs.netlify.com>)", "name": "", "is_accepted": true } ]

[ { "text": "you only get it if you request it with showavatar=true as query param.", "name": "", "is_accepted": true } ]

[ { "text": "issueservice (and most of the other *service) enforces permissions (and other validations). in this case it’s that anonymous doesn’t have the rights to create issues.\n\nthe workaround is to use issuemanager or other service. take a look at the source of issueservice to see what it is doing.", "name": "", "is_accepted": true } ]

[ { "text": "hi [@sven.schatter](/u/sven.schatter), we had a release pipeline issue for 2.1.9 where [only the parent pom](https://mvnrepository.com/artifact/com.atlassian.connect/atlassian-connect-spring-boot/2.1.9) got sync’d to maven central. it should be fixed within a day or two.\n\nregarding the release announcements here on the developer community, i only posted them to give higher-impact releases an extra push. since [2.1…](https://community.developer.atlassian.com/t/39240)", "name": "", "is_accepted": true } ]

[ { "text": "hi [@matthewebert](/u/matthewebert),\n\nthis capability is not yet supported by forge so i have created [frge-208](https://ecosystem.atlassian.net/browse/frge-208) to request it.\n\nregards,\n\ndugald", "name": "", "is_accepted": true } ]

[ { "text": "the same way that you should update a public rest api to support both the old and new versions applies here as well.\n\nessentially, here are some tips:\n\nfor iframes, if you add something new, create a new resource to serve your html, css and js. always maintain the old version of the webpage resourc…", "name": "", "is_accepted": true } ]

[ { "text": "looks like a classloader issue. i’ve decided to use active objects instead.", "name": "", "is_accepted": true } ]

[ { "text": "hmm, it works again somehow.\n\ni restarted the ubuntu wsl2 in my windows system: wslconfig /t ubuntu-20.04 (reopen ubuntu after this command), and my forge tunnel works again, i don’t know if the ubuntu restarting really help here, or i have lucky from something else.\n\nbut one thing i don’t understan…", "name": "", "is_accepted": true } ]

[ { "text": "[your macro can detect whether it is being exported](https://developer.atlassian.com/server/confluence/how-can-i-determine-the-context-my-macro-is-being-rendered-in/). if your macro is being exported you should return html that resembles your dynamic macro as best as possible. :slight\\_smile:", "name": "", "is_accepted": true } ]

[ { "text": "thank you for your answer! i just figured it out.\n\ni copied the request body out of the [documentation](https://developers.trello.com/reference/#customfields) and didn’t recognize the missing quotation marks. i tried it by adding the key and token to the body just like in the custom fields value set, update and remove request.\n\nit worked!\n\nso my request l…", "name": "", "is_accepted": true } ]

[ { "text": "[@decreelabs](/u/decreelabs),\n\nno. currently, it is not possible to securely access jsm and insight api with forge. there isn’t anything on [the public roadmap](https://www.atlassian.com/roadmap/cloud?selectedproduct=jiraservice&search=insight) specific to insight and forge.", "name": "", "is_accepted": true } ]

[ { "text": "if you want to deploy to nexus using a deployment project on bamboo and reuse the artefact you can use <http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html>\n\notherwise you are right, you can just call mvn deploy in the first place, no need to have a deployment project for that.\n\n…", "name": "", "is_accepted": true } ]

[ { "text": "do you have any apps installed that may be past their trial date?", "name": "", "is_accepted": true } ]

[ { "text": "hello\n\nthat was the tutorial i was following yes. the code provided with that tutorial doesnt appear to work as provided. i did also attempt to edit that properties client file to no avail. perhaps its something that someone on the atlassian team can examine as i believe that i was not the only one …", "name": "", "is_accepted": true } ]

[ { "text": "[@maciej.dudziak](/u/maciej.dudziak), this is a known issue. please watch [ac-2448](https://ecosystem.atlassian.net/browse/ac-2448).", "name": "", "is_accepted": true } ]

[ { "text": "it does appear like i will have to use a 3rd party to store files. i downloaded a trial version of insight inventory management (cloud version) and all uploaded images point towards their own servers.\n\nthis is pretty disappointing coming from the server version, as it significantly increases the amo…", "name": "", "is_accepted": true } ]

[ { "text": "hey,\n\nmake sure that your web resource contains the following dependency: <dependency>jira.webresources:jqlautocomplete</dependency>\n\nand that it is available in the context:\n\n<context>atl.admin</context>\n\nhope that this helps!", "name": "", "is_accepted": true } ]

[ { "text": "hi [@nkemjikagwacham](/u/nkemjikagwacham),\n\nyou’ll need to use the second return value of usestate to update the projects.\n\nit should look something like…\n\nconst [projects, setprojects] = usestate(fetchrec);\n\nreturn (\n\n<fragment>\n\n// display or map projects records here\n\n<button text=\"refresh records\" onc…", "name": "", "is_accepted": true } ]

[ { "text": "i have been able to resolve this issue… 2 things\n\nfrom docs i understood that only relative url needs to be passed for creation of jwt token but it turns out it needs the full url with domain as well\n\nincrease the token lifespan from 3 minutes.\n\nthe custom field i had created was “read\\_only” as i on…", "name": "", "is_accepted": true } ]

[ { "text": "for anyone else coming to this from google …\n\nthis line … jsonheader = {“content-type”: ‘application/json’} no longer works\n\nit is now … jsonheader = {“content-type” => ‘application/json’}", "name": "", "is_accepted": true } ]

[ { "text": "i have a similar problem at the moment too: when the macro is viewed on a historical version, i get only the page id of the historical version but some of the content i want to access (attachments, custom content) are always stored under the id of the current version\n\nit seems to be surprisingly har…", "name": "", "is_accepted": true } ]

[ { "text": "can you try with java8? (it looks like you’re using java 11)", "name": "", "is_accepted": true } ]

[ { "text": "you can query the storage.\n\nconst queryresults = await storage\n\n.query()\n\n.where('key', startswith('key'))\n\n.getmany();\n\n<https://developer.atlassian.com/platform/forge/runtime-reference/storage-api-query/>\n\nedited:\n\ni think you are doing it wrong somehow. here you are using the same key “key1” for…", "name": "", "is_accepted": true } ]

[ { "text": "i found a solution myself and posted it as a reply to my community question here:\n\n[image]\n\n[how to create a new version of confluence page via java api / scriptrunner?](https://community.atlassian.com/t5/confluence-questions/how-to-create-a-new-version-of-confluence-page-via-java-api/qaq-p/1358139#u1386292)\n\ni am trying to manipulate a confluence page via adaptavist scriptrunner for confluence and the java api. changing the conte…", "name": "", "is_accepted": true } ]

[ { "text": "the issue is that you’re viewing the data as 2 different things - configuration and issues. jira views it as the same. migrating things in 2 steps will be problematic logistically (think custom fields - maybe the first instance doesn’t know about it but the second one has it as a required field).\n\ni…", "name": "", "is_accepted": true } ]

[ { "text": "indeed, that was the view template issue. adding the following line to the module and the corresponding view template solved the problem.\n\n<resource type=\"velocity\" name=\"view\" location=\"templates/postfunctions/recalculate-issue-deadlines-post-function.vm\"/>\n\n[[image]](https://aws1.discourse-cdn.com/atlassiandeveloper/original/3x/a/3/a3c30781e64e1bd2da968bf20741d4cd73bf811c.png \"image.png\")", "name": "", "is_accepted": true } ]

[ { "text": "bitbucket server apps are always global. depending on which modules you’re using - they can be filtered down to be repository specific though. in your case - make sure to look at <https://developer.atlassian.com/server/bitbucket/reference/plugin-module-types/repository-hook-plugin-module/> since those…", "name": "", "is_accepted": true } ]

[ { "text": "[image] scottreopelle:\n\ncurl -d- -u [email protected]:my-api-token -x get -h \"content-type: application/json\" https://my-site.atlassian.net/rest/api/3/users/search\n\nin this, username seems to be incorrect. it’s not supposed to be [email protected] but something like u…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@andrewtyson](/u/andrewtyson),\n\n[noauthenticationit](https://bitbucket.org/atlassian/atlassian-connect-spring-boot/src/master/atlassian-connect-spring-boot-it/atlassian-connect-spring-boot-minimal-it/src/test/java/com/atlassian/connect/spring/it/auth/noauthenticationit.java) provides an example for you to follow:\n\n@springboottest(..., properties = \"atlassian.connect.require-auth-exclude-paths=/no-auth\")\n\ni double-checked that the test passes fine with mockmvc as well (and fails without the require-auth-exclude-paths property):\n\nmvc.p…", "name": "", "is_accepted": true } ]

[ { "text": "i was having the same issue. in my case, i was able to fix (or at least, work around) it by first signing out of my atlassian account (e.g. from <https://start.atlassian.com/>) then signing in again. i was then able to authorise the app as expected.", "name": "", "is_accepted": true } ]

[ { "text": "thanks for your replies. i already found the solution from below, it is working fine.\n\n[[gok]](https://stackoverflow.com/users/899188/gok)\n[export to csv using jquery and html](https://stackoverflow.com/questions/16078544/export-to-csv-using-jquery-and-html)\n\njquery, html, csv, export\n\nasked by\n\n[gok](https://stackoverflow.com/users/899188/gok)\n\non [08:56am - 18 apr 13](https://stackoverflow.com/questions/16078544/export-to-csv-using-jquery-and-html)", "name": "", "is_accepted": true } ]

[ { "text": "yes, we also noticed it.\n\nyou may check for more information the status page - <https://developer.status.atlassian.com/>\n\natlassian publishes information about the outage and the recovery steps.\n\nif you want to get notification you may subscribe to updates for any service that is down.\n\nregards,\n\nanni…", "name": "", "is_accepted": true } ]

[ { "text": "in case it isn’t clear, “jira rest java client*” is jrjc. atlassian does not make a similar library to work with jira cloud.\n\ni wrote up how to generate a client library from our open api spec for jira cloud. note that this won’t provide a drop-in replacement if you were previously using jrjc.\n\nsee [h…](https://community.atlassian.com/t5/jira-articles/generating-a-rest-client-for-jira-cloud/ba-p/1307133)", "name": "", "is_accepted": true } ]

[ { "text": "ok so success!!! if we modify the manfest.yml file to remove the data elements as we your commit on the risk assessment field example, it now works as expected and is visible.\n\nthis is the code i removed.\n\ndata:\n\nstorage:\n\nissueproperty:\n\nkey: forgeriskfieldvalue\n\nreadonly:…", "name": "", "is_accepted": true } ]

[ { "text": "[image] mattlassian:\n\nor maybe this is what happens when the user who created the comment is deleted?\n\ni’m 99% sure this is the case.\n\nit looks like the membercreator field is pulled at time of need from the db. for instance, if you go and change your name, the new name will be reflected in all…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@grzegorz.tanczyk](/u/grzegorz.tanczyk) and [@marc](/u/marc),\n\nmy interpretation is that this feature only restricts the connections made by users to the product and as such, i don’t believe there will be any direct impact on apps.\n\nusers also won’t be able to access that product programmatically via the apis\n\nthis statement r…", "name": "", "is_accepted": true } ]

[ { "text": "the js and css files are no longer combined. this isn’t something you’d want to do in production (batching helps to speed things up). in development mode you don’t really want this since it will have to rematch things each time you make a change in them (and it will be slower) so each js file is loa…", "name": "", "is_accepted": true } ]

[ { "text": "i installed c++ for visual studio and it fixed the problem.\n\nfollowed the advice here:\n\n[build error on windows 10 - trk0005: failed to locate: \"cl.exe\"](https://github.com/lovell/sharp/issues/341)\n\nopened 12:15pm - 21 jan 16 utc (utc)\n\nclosed 05:16am - 23 jan …", "name": "", "is_accepted": true } ]

[ { "text": "i have that experience about apache poi such as only latest version of that framework works with atlassian confluence server and previous versions do not work. so possible some how latest version of the jira server is changed that way apache poi 3.16 do not work anymore.", "name": "", "is_accepted": true } ]

[ { "text": "when attaching any select2 to a input, you must use <input type='hidden' name='yourname' id='yourid' /> instead of a select element.\n\nsimply put, for a static field, use select elements. for a dynamic field, use input type='hidden'.", "name": "", "is_accepted": true } ]

[ { "text": "hi [@m.abdel-mola](/u/m.abdel-mola),\n\nto do that, you should look at the rich text editor developer documentation which can be found here: <https://developer.atlassian.com/jiradev/jira-platform/guides/rich-text-editor/tutorial-writing-plugin-for-rich-text-editor-in-jira>\n\nyou can hook into the editor and do fancy things…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@mitch.terlisner](/u/mitch.terlisner)\n\nthe callback based conditions you are referring to were called “remote conditions” and they were removed some timeago. back then the prefined conditions were rather limited, entity properties didn’t exist, but there are a lot more conditions now and [jira expressions](https://community.developer.atlassian.com/t/introducing-jira-expressions/20006) provide a po…", "name": "", "is_accepted": true } ]

[ { "text": "thanks for the replies.\n\nin outgoing authentication on the jira application, the checkbox was unchecked for “enable outgoing 2-legged oauth with impersonation requests”.\n\nonce checked, fixed my error.\n\n[[image]](https://aws1.discourse-cdn.com/atlassiandeveloper/original/3x/d/f/dfcfbcb358c7ba97afa15db6ddfb0352ed36c52c.png \"image\")", "name": "", "is_accepted": true } ]

[ { "text": "i think the header would have to be specified on each request:\n\nap.request({\n\n\"url\": \"/sompath\",\n\n\"type\": \"get\",\n\n\"headers\": \"{'x-atlassian-force-account-id', true}\",\n\n\"cache\": false\n\n});", "name": "", "is_accepted": true } ]

[ { "text": "hi [@ushur](/u/ushur) - check out our documentation on managing your app listing here:\n\n<https://developer.atlassian.com/platform/marketplace/listing-and-managing-apps/>\n\nnote that there are two spots you can update app information after clicking “manage app” from your app listing page:\n\napp level - by clicking …", "name": "", "is_accepted": true } ]

[ { "text": "works now! thank you!", "name": "", "is_accepted": true } ]

[ { "text": "hey [@aragot](/u/aragot),\n\nto add to neil and daniel comments.\n\nall of this is one single question, as you’ve guessed\n\nthanks for asking :slight\\_smile: this is a very valid question and it’s important for application stability. to give you are a short and quick answer: add limits for everything and stream as m…", "name": "", "is_accepted": true } ]

[ { "text": "my team mate has found the solution to this problem. using the following javascript, you can open the create issue dialog with a callback. once all the issues have been created, the callback is called with the created issue data.\n\nwrm.require([\"wr!com.atlassian.jira.jira-quick-edit-plugin:quick-crea…", "name": "", "is_accepted": true } ]

[ { "text": "hello ali,\n\nthe can be migrated field will be active after the release of ccma in feb and jcma in april.\n\nyou will also need to update your listing in marketplace using the migrations api documented here\n\n[https://developer.atlassian.com/platform/marketplace/rest/api-group-migrations/#api-group-migr…](https://developer.atlassian.com/platform/marketplace/rest/api-group-migrations/#api-group-migrations)", "name": "", "is_accepted": true } ]

[ { "text": "hi [@jan](/u/jan),\n\nit seems to be ok on my end when i ran atlas-run-standalone --product bitbucket and upload the jar file.\n\n[[image]](https://aws1.discourse-cdn.com/atlassiandeveloper/original/3x/7/7/77a168c6de8cf34ddf5a2388638a49da8de2cb17.png \"image\")\n\ntrying to redeploy via quickreload, by running atlas-package on a different terminal also was successful in redeploying the app. the only changes i made were to remove the tw…", "name": "", "is_accepted": true } ]

[ { "text": "there’s an active incident that’s likely to be related. i had the same problem with missing triggers in the past 8hrs.\n\n<https://confluence.status.atlassian.com/>", "name": "", "is_accepted": true } ]

[ { "text": "hi [@davidm](/u/davidm) – thanks for reporting this. we’ve now turned off the feature flag that caused this. please let us know if you’re still experiencing any issues.\n\nthanks,\n\namaresh", "name": "", "is_accepted": true } ]

[ { "text": "the toggle button was introduced in aui 5.9 (<https://docs.atlassian.com/aui/7.0.0/docs/toggle-button.html> ). according to <https://bitbucket.org/atlassian/aui-adg/wiki/versions/product-version-matrix> aui 5.9 wasn’t used until jira 7.2. in this case you’d probably need to create your own version of th…", "name": "", "is_accepted": true } ]

[ { "text": "typically you would be using the classes issuetypeservice, issuetypemanager, customfieldservice, and customfieldmanager to achieve this.", "name": "", "is_accepted": true } ]

[ { "text": "answering my own question for others who come across same problem with me. i moved the logic from pluginenabledevent to lifecyleaware’s start() method, at which time all startable components should have been initialized.", "name": "", "is_accepted": true } ]

[ { "text": "hi, [@paul](/u/paul).\n\nregarding the order of issues returned depending on the order in the request, i believe it is so. i made a quick test and it holds true as well.\n\nregarding the error during bulk creation of issues, if one issue fails due to invalid issue type for example, all the others will still be cre…", "name": "", "is_accepted": true } ]

[ { "text": "for those wondering i figured out how to do this, i added a rest service that the javascript calls.\n\n<https://developer.atlassian.com/server/framework/atlassian-sdk/developing-a-rest-service-plugin/>", "name": "", "is_accepted": true } ]

[ { "text": "hello,\n\nquite similar … but i have found the culprit: we use and iterate over a cursor that missed the condition and yielded this bogus results… i wished the api for that would be less convoluted and harder to get wrong as we apparently did: if i have a reference for the cursor it seems really weird…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@maciej.dudziak](/u/maciej.dudziak) ,\n\ni’ve created a minimal example for this which seems to work. you can install it from <https://dx-automation-action.glitch.me/connect.json> and you can inspect the code at [glitch :･ﾟ✧](https://glitch.com/edit/#!/dx-automation-action).\n\nregards,\n\ndugald", "name": "", "is_accepted": true } ]

[ { "text": "hi [@jordanglassman](/u/jordanglassman),\n\ni discussed with my team on this and your confusion is understandable. let me try clarifying those:\n\nas mentioned in [3lo docs](https://developer.atlassian.com/cloud/jira/platform/oauth-2-authorization-code-grants-3lo-for-apps/#3-2-construct-the-request-url), “requests that use oauth 2.0 (3lo) are made via api.atlassian.com (not https://your-domain.atlassian.net )”, you will have to use api.atlassian.com …", "name": "", "is_accepted": true } ]

[ { "text": "for server,\n\nyou’ll need to write your own condition class (extend <https://docs.atlassian.com/software/jira/docs/api/7.6.0/com/atlassian/jira/plugin/webfragment/conditions/abstractwebcondition.html> ) and then on the project object or on the issue object (depending on the location that you’re doing t…", "name": "", "is_accepted": true } ]

[ { "text": "we resolved this. the issue was on our side. the root cause for this was that we were doing the request using an outdated and buggy [jira-ruby](https://github.com/sumoheavy/jira-ruby) client version (v.1.7).\n\nfix was introduced in v.1.7.1 - [here is the fix](https://github.com/sumoheavy/jira-ruby/commit/0302694ae20bb8e8e37e8b16d11ece4a0c027e9a).\n\nwe were also able to a get correct response without using a jira-ruby client.", "name": "", "is_accepted": true } ]

[ { "text": "here is sanitised version of an old editor markup:\n\n<form action=\"\" class=\"aui\">\n\n<div class=\"form-body\">\n\n<div class=\"field-group aui-field-wikiedit test-input\">\n\n<label for=\"test\">test</label>\n\n<div class=\"jira-wikifield\" renderer-type=\"atlassian-wiki-renderer\" issu…", "name": "", "is_accepted": true } ]

[ { "text": "christoffer posted the solution to the problem [here](https://community.developer.atlassian.com/t/how-to-disable-collaborative-editing-via-amps-when-developing/8057/4)\n\n<systempropertyvariables>\n\n<atlassian.darkfeature.site-wide.synchrony.opt-in.disable>true</atlassian.darkfeature.site-wide.synchrony.opt-in.disable>\n\n<atlassian.darkfeature.site-wide.shared-drafts.disable>true</atlassian.darkfeature.site-wide.sh…", "name": "", "is_accepted": true } ]

[ { "text": "hi rhys,\n\ni think it was asked already, but can’t find proper link, so accessing jira’s api on connect\\_addon\\_enabled event works for us with no problems, using nodejs atlassian-connect-express, e.g.:\n\naddon.on('connect\\_addon\\_enabled', function (event, body, req) {\n\nnote, you may need to add connect\\_…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@alexeygritskevich](/u/alexeygritskevich),\n\nthanks for reporting this. i’ve created <https://jira.atlassian.com/browse/jracloud-74975> to track this problem.\n\nregards,\n\ndugald", "name": "", "is_accepted": true } ]

[ { "text": "looks like it’s almost working -> you can see from stack trace that operation was successful (success method was called), but there’s some problem with deserializing response. response is not used in your case so exception should be gone after you remove this line:\n\nresponse = json.parse(response);\n\n…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@raimonds.simanovskis](/u/raimonds.simanovskis) ,\n\nthe jira cloud team have indicated they are going to fix the thumbnail aspect ratio today. in my experience, it will take a few business days to get the fix rolled out.\n\nregards,\n\ndugald", "name": "", "is_accepted": true } ]

[ { "text": "you need to include apache commons lang in your dependencies; it appears to be missing from atlassian’s jwt library.\n\n<dependency>\n\n<groupid>commons-lang</groupid>\n\n<artifactid>commons-lang</artifactid>\n\n<version>2.6</version>\n\n</dependency>", "name": "", "is_accepted": true } ]

[ { "text": "hi [@rr1](/u/rr1),\n\ni think that this is hard-wired :frowning: . maybe this answers you question:\n\n[image]\n\n[how to make my rest resource appear as public in the rest api browser?](https://community.atlassian.com/t5/answers-developer-questions/how-to-make-my-rest-resource-appear-as-public-in-the-rest-api/qaq-p/562585)\n\ni am documenting a jira plugin rest api resources and am using the rest api browser (rab) to verify my documentation. in th…", "name": "", "is_accepted": true } ]

[ { "text": "hi everyone,\n\na product issue is created for this. please see progress in <https://ecosystem.atlassian.net/browse/amps-1503>\n\ncheers,\n\nanne", "name": "", "is_accepted": true } ]

[ { "text": "i don’t know why it is jira-maven-plugin in the screenshot but actually i had already corrected this.\n\ni managed to solve it by changing to correct jira servicedesk version and also adding jira software.\n\nlink for reference of solution:\n\n[image]\n\n[update latest amps documentation for…](https://community.developer.atlassian.com/t/update-latest-amps-documentation-for-jira-service-desk/30350)", "name": "", "is_accepted": true } ]

[ { "text": ":blush: i find it: jira.navigator.pluggable.items", "name": "", "is_accepted": true } ]

[ { "text": "after some searching inside the api i’ve found changedclause interface where i can do what i was looking for. afterwards, was necessary to include jira-core dependency to implement it.\n\nif someone was looking for an answer, that’s it. and thanks for any effort.", "name": "", "is_accepted": true } ]

[ { "text": "hi [@jbevan](/u/jbevan), we the url is now <https://atlaskit.atlassian.com/packages/core/flag>", "name": "", "is_accepted": true } ]

[ { "text": "hi michael,\n\nthanks very much for the example code.\n\nif i change the contenttype to:\n\ncontenttype: 'multipart/form-data',\n\nthen it seems to work for me. can you see if that helps please?\n\nregards,\n\ndavid boyd\n\natlassian connect", "name": "", "is_accepted": true } ]

[ { "text": "this one i can answer! short story: you might not be able to, but it’s not atlassian’s fault.\n\nyou don’t need to use ap.request(). you can simply use the feature of your browser – the xmlhttprequest or jquery’s wrapper if you have jquery:\n\n$.ajax({url: '...'}).success(function(data) { ... }).\n\nthe r…", "name": "", "is_accepted": true } ]

[ { "text": "this is intended and depends on how the hook was configured:\n\nyou can write hooks that are only called for pushes, or\n\nyou can also write hooks that are called for any ref change\n\nthe ‘mergeability’ check includes a so-called ‘dry-run’ invocation of the repository hook. based on this scenario, at th…", "name": "", "is_accepted": true } ]