Datasets:

---

clips

/

mqa

like 52

Follow

CLiPS 10

[ { "text": "ok, got it.\n\nit must be ap.flag.create({ instead of ajs.flag({\n\nthanks [@alexter\\_pr](/u/alexter_pr)", "name": "", "is_accepted": true } ]

[ { "text": "[@paul](/u/paul) given that the p2 infrastructure really differs from connect i would not recommend trying to merge these two. the best way to share a code base is:\n\nshare static resources, more specifically create a front-end which only consumes data from an api.\n\nrecreate the api (both in terms of endpoints …", "name": "", "is_accepted": true } ]

[ { "text": "dc is just another license on installation. use evaluations licenses as they are valid for a month at least\n\nfor local testing:\n\nuse docker (the [official image](https://hub.docker.com/r/atlassian/confluence-server/) just works fine)\n\nit is also “quite” easy to set up a local cluster with docker. just share the database and shared home with all nodes.\n\n[h…](https://www.dropbox.com/s/dvuvdt3652uk5gd/datacenter-docker.zip?dl=0)", "name": "", "is_accepted": true } ]

[ { "text": "oh, my dear fellow, [i feel your pain](https://community.developer.atlassian.com/t/issue-type-schemes-via-rest/1270).\n\nwhat we’ve done is to add the issue type, and display a warning in the context of the project(s) that the issue type needs to be added to the relevant issue type scheme. it’s sub-optimal.", "name": "", "is_accepted": true } ]

[ { "text": "hello [@iragudo](/u/iragudo)\n\nthank you for your help. i tried your method but it didn’t work out well. (i tried forge deploy before and after your suggested “npm install”, i got the same error)\n\nthough i found one walkaround. renaming .gitignore file to something else. with this workaround, i could deploy the ap…", "name": "", "is_accepted": true } ]

[ { "text": "[image] dmehers:\n\ni decided to fix this by adding a limit=500 when fetching the cards\n\nthis is the correct thing to do. using the since and before parameters, you can continue to page through results to get everything. there is a brief mention of paging here: [https://developers.trello.com/docs/…](https://developers.trello.com/docs/api-introduction#section-paging)", "name": "", "is_accepted": true } ]

[ { "text": "i don’t think there’s a public api which allows you to achieve the things you want to.\n\nif you want to write a plugin to allow such things, please refer to writing a plugin with [rest plugin module](https://developer.atlassian.com/docs/atlassian-platform-common-components/rest-api-development/rest-plugin-module)\n\nhowever, i encourage you to use [bamboo specs](https://docs.atlassian.com/bamboo-specs-docs/latest/) which allow you to modify bamboo configuration from java …", "name": "", "is_accepted": true } ]

[ { "text": ":upside\\_down\\_face: oh i get it now… so i worked this out i think… read only custom fields can not be directly updated via the api. rather, they serve as a reference or pointer to map another issue property. the mapped property can be either an existing issue property or in my case, an entity propert…", "name": "", "is_accepted": true } ]

[ { "text": "i believe that to make use of await, you need to make the function async so this:\n\n[image] jimmyseddon:\n\nfunction getsearchresults(searchapi) {\n\nbecomes:\n\nasync function getsearchresults(searchapi) {\n\nmore on async/await: [async/await](https://javascript.info/async-await)\n\ncurious to see if that changes anything.", "name": "", "is_accepted": true } ]

[ { "text": "i think it’s been discussed here mostly: [a peek into marketplace's new app listing page](https://community.developer.atlassian.com/t/a-peek-into-marketplaces-new-app-listing-page/48229)", "name": "", "is_accepted": true } ]

[ { "text": "technically, the answer should be “in accordance with the atlassian privacy policy” because that was the driving force behind that number and it is the rule we follow for all data.\n\nbut i understand the desire for data lifecycle to be more clearly communicated in the forge docs. i’ll bring this to o…", "name": "", "is_accepted": true } ]

[ { "text": "hey [@anton2](/u/anton2) seems to be intentional and not a bug: <https://blog.developer.atlassian.com/change-notice-padding-update-for-jira-cloud-navigation-ui/>\n\nbut it does mention it is a temporary fix.", "name": "", "is_accepted": true } ]

[ { "text": "[image] driver:\n\n“installation failed. the app defined an unknown module (blueprints).”\n\nhello [@driver](/u/driver), this error occurs when you install the app in a non-confluence product. i experienced the exact error before when i accidentally removed /wiki in the upm url (<baseurl>/wiki/plugins/servlet/…", "name": "", "is_accepted": true } ]

[ { "text": "here you go.\n\n<https://bitbucket.org/server-platform/ao/>\n<https://bitbucket.org/server-platform/ao-plugin/>\n\np.s. thanks [@kbrazulewicz](/u/kbrazulewicz) & [@aswan](/u/aswan).", "name": "", "is_accepted": true } ]

[ { "text": "this is exactly what the config.json file is for. you specify the localbaseurl in the development and the production object and the correct value will be used depending on which env you have set.\n\nfor the frist error, have you filled your store values with the correct connection string in the “confi…", "name": "", "is_accepted": true } ]

[ { "text": "hi all,\n\nsorry for the late reply but we have been really busy in the last months launching the new version of our atlassian cloud add-ons.\n\nthanks you all for the useful hints! we finally managed to correctly include and reference the fonts and the css library. the main problem was the relative url…", "name": "", "is_accepted": true } ]

[ { "text": "bitbucket.web.repository.banner is a web-panel, not a client-web-panel.", "name": "", "is_accepted": true } ]

[ { "text": "if anyone comes across this post, i think i found a possible culprit:\n\nif you configure a trigger in a workflow, for example, link a bitbucket account and create a trigger “transition issue when branch created”. the issue updated webhook payload will not contain any user property.\n\nthis is the email…", "name": "", "is_accepted": true } ]

[ { "text": "[@spall](/u/spall) here we go!\n\n[image]\n\n[new external permissions, authorize method, cli improvements, and bug fixes](https://community.developer.atlassian.com/t/new-external-permissions-authorize-method-cli-improvements-and-bug-fixes/49409/7) [forge announcements](/c/forge/forge-announcements/62)\n\nhi [@dennymiller](/u/dennymiller)\n\nthanks for reaching out.\n\nyou can use the general search endpoint instead: /wiki/rest/api/search?cql=<your\\_query\\_here>\n\n(see: [search …](https://developer.atlassian.com/cloud/confluence/rest/api-group-search/#api-group-search)", "name": "", "is_accepted": true } ]

[ { "text": "[@ashishghone](/u/ashishghone)\n\nthis is likely due to [a performance issue](https://status.bitbucket.org/incidents/z029156p1svh) we had this morning.\n\neric henry\n\ndevelopment team lead, bitbucket cloud", "name": "", "is_accepted": true } ]

[ { "text": "we are aware of this problem and the dac team is working on resolving this.", "name": "", "is_accepted": true } ]

[ { "text": "the issue is resolved.", "name": "", "is_accepted": true } ]

[ { "text": "i stumbled onto this [confcloud ticket](https://jira.atlassian.com/browse/confcloud-65355) and in the internal comments was a statement that this can be handled already like so:\n\n/wiki/rest/api/search?cql=user.accountid%20in(<accountid>,<accountid>)\n\nlet me know if that works for you?\n\nas for the bulk endpoint not being available in apps…i’ll bring th…", "name": "", "is_accepted": true } ]

[ { "text": "this was “user error”. the changes to web hooks on atlasian-connect.json don’t populate right away when the app is published in the marketplace.", "name": "", "is_accepted": true } ]

[ { "text": "you need to expose the soy template to the page in the atlassian-plugin.xml\n\n<web-resource key=\"\" name=\"\" >\n\n...\n\n<dependency >confluence.web.resources:ajs</dependency >\n\n...\n\n<context >page</context >\n\n...\n\n<resource type=\"download\" name=\"dialog.js\" location=\"<path>/dialog.soy\" />…", "name": "", "is_accepted": true } ]

[ { "text": "not at this time, no. but we are working on bringing a three-legged oauth (3lo) to jira cloud. it’s currently listed as in progress on the [jira cloud platform api - public roadmap](https://trello.com/c/xfys3iku/2-simpler-authentication-options-3lo)\n\nthis work is also currently being worked on for stride apps and is the foundation for jira using it. it’s currently i…", "name": "", "is_accepted": true } ]

[ { "text": "to be honest… i think most successful vendors are the ones that stick around long enough to have clocked the hours required to either actually know by experience, have seen the product change historically, are aligned with atlassian product development and have become really really good at searching…", "name": "", "is_accepted": true } ]

[ { "text": "finally found the answer myself. you need to migrate the schema in the upgrade task. in the migrate method run ao.migrate(.class);", "name": "", "is_accepted": true } ]

[ { "text": "i added a condition to not display the webpanel if database is empty, and it just worked.\n\n/**\n\n* determine whether the web fragment should be displayed\n\n*\n\n* @param context the optional map of parameters specified in xml.\n\n* @return true if the user should see the fragment, false otherwise\n\n*/…", "name": "", "is_accepted": true } ]

[ { "text": "easiest way is to call the rest api via ajax and if result is empty, no space exist with this key.\n\nexemple :\n\nfunction existproject(spacekey) {\n\najs.$.ajax({\n\nurl: ajs.contextpath() + \"/rest/api/space?spacekey=\" + spacekey,\n\ntype: \"get\",\n\ndatatype: \"json\",\n\n…", "name": "", "is_accepted": true } ]

[ { "text": "hi, [@matthias1](/u/matthias1).\n\nchecking the rest api docs for [get locale](https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-mypreferences-locale-get), it says that\n\napps cannot access this rest resource.\n\nwhich means that there is nothing wrong with your code and this is the expected behavior. you can try [get current user](https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-myself-get), it also returns the locale for you.\n\nbest regards,\n\nian", "name": "", "is_accepted": true } ]

[ { "text": "hi [@m.herrmann](/u/m.herrmann),\n\nconnect auth and forge work differently and require different scopes. you’ll need to add the connect scope equivalents to your manfest, e.g. read:connect-jira or write:connect-jira - see [this section](https://developer.atlassian.com/platform/forge/build-a-connect-on-forge-app/#step-1--get-the-sample-app) of the connect-on-forge tutorial for more.", "name": "", "is_accepted": true } ]

[ { "text": "you can see the duedates of your checklist items by calling the\n\nget /1/cards/{id}/checkitem/{idcheckitem}. the due dates should be a datetime value under the due field.\n\nyou can update a duedate of a checkitem using the following api call:\n\nput /1/cards/{idcard}/checklist/{idchecklist}/checkitem/{i…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@nasmussadat](/u/nasmussadat) , welcome to the developer community!\n\ni was able to replicate the same error you got when i did:\n\nclone the repo\n\nrun forge register\n\nrun forge deploy\n\nto fix the issue, you missed calling npm install before running forge deploy. that should do the trick.\n\ncheers!\n\nian", "name": "", "is_accepted": true } ]

[ { "text": "probably it just gets cached somehow. it’s doing now.", "name": "", "is_accepted": true } ]

[ { "text": "hi @fiedlermarius,\n\nsimply put, it is not possible to implement custom authentication for atlassian cloud applications. among other reasons, atlassian has a shared authentication layer for our cloud services called atlassian account, so jira cloud does not even have apis that you could extend. addit…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@tbinna](/u/tbinna),\n\nwe just added attachment\\_created and attachment\\_deleted events to jira a couple weeks ago and simply haven’t updated the documentation yet. we will get to it asap.\n\ndave", "name": "", "is_accepted": true } ]

[ { "text": "hello, [@mertturkoglu](/u/mertturkoglu),\n\nit seems you are not using the correct key of your field. if you head over to [the documentation](https://developer.atlassian.com/platform/forge/manifest-reference/modules/#field-lifecycle) you will find the following passage there:\n\nthe created field has its key set to {app-id-uuid}\\_\\_{environment}\\_\\_{extension-key} , where:\n\n{app-id-uuid} is the tail part of your ap…", "name": "", "is_accepted": true } ]

[ { "text": "it doesn’t appear that you can get a list of all of the boards your member is watching. is there a place in the trello ui that this is available? i tend to start looking at the network requests happening for things in the ui to lead me to which api resource is being used. \nhowever, you can definitel…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@ajay](/u/ajay) ,\n\ni think this error is coming from [here](https://bitbucket.org/atlassian/atlassian-connect-js/src/9cc298035fdb6ce8ac82a613acdcf6a25a33d761/src/host/utils/webitem.js#lines-74). it only goes into this path if there’s hash fragment in the webitem url. i wonder if the leading/ in your /index.html?board.id={board.id}/#/standup webitem url hash fragment is causing the issue?\n\nregards,\n\ndugald", "name": "", "is_accepted": true } ]

[ { "text": "hi [@davidm](/u/davidm), this may be due to you having default user groups pending to approve in the user management section of your site administration. we would prefer for add-on installation not to fail in these cases, which is tracked in [ac-2320](https://ecosystem.atlassian.net/browse/ac-2320).", "name": "", "is_accepted": true } ]

[ { "text": "the reason automation for jira can act as a user is because it is an atlassian connect app. it does not use api keys. the connect framework creates special service accounts for apps (hence the “automation for jira” user) and allow for user impersonation if the act\\_as\\_user scope is set upon installat…", "name": "", "is_accepted": true } ]

[ { "text": "not an atlassian but the only advice i’ve heard from atlassian is to follow the headers. ie when they return rate limit exceeded header - then back off. that said without knowing much about your script - if you’re not triggering the 300 in parallel and doing the sleep in between - you’re fine. you’r…", "name": "", "is_accepted": true } ]

[ { "text": "hi jeroen,\n\ni do it this way:\n\n\"webitems\" : [{\n\n\"name\": {\n\n\"value\": \"report problem\"\n\n},\n\n\"key\": \"bitbucket\",\n\n\"url\": \"/bitbucket?v=3\",\n\n\"location\": \"none\",\n\n\"context\": \"addon\",\n\n\"target\": {\n\n\"type\": \"dialog\"\n\n}\n\n}]", "name": "", "is_accepted": true } ]

[ { "text": "hi [@candid](/u/candid) ,\n\ni’ve reproduced this and created <https://jira.atlassian.com/browse/confcloud-72463> for the confluence ecosystem team to address.\n\nregards,\n\ndugald", "name": "", "is_accepted": true } ]

[ { "text": "thank you vary much!!!\n\nthe cause of the problem is that my ao entity did not directly inherit net.java.ao.entity.\n\nchange to\n\npublic interface usagelogao extends net.java.ao.entity\n\nthe problem is solved!\n\nmy original code is\n\npublic interface entity extends rawentity<long>\n\n{\n\n@autoincrement\n\n…", "name": "", "is_accepted": true } ]

[ { "text": "[@yvesriel](/u/yvesriel) [@boris](/u/boris) [@david.toussaint](/u/david.toussaint) [@raimonds.simanovskis](/u/raimonds.simanovskis) thanks all for flagging this issue. we have identified the bug and implemented the fix as necessary. could you please try again and confirm it is working as expected now?\n\ncheers,\n\nsean", "name": "", "is_accepted": true } ]

[ { "text": "based on the error message i see when trying to repro it, i don’t think you can do any sort of pathing in your app’s manifest.yml:\n\nfunction handler property ‘test/best.handler’ must be in format <module>.<function>\n\nhowever, a workaround for this might be to have a top-level module that you impor…", "name": "", "is_accepted": true } ]

[ { "text": "[@philipfeldmann](/u/philipfeldmann) you can achieve that using the update content api: <https://developer.atlassian.com/cloud/confluence/rest/api-group-content/#api-api-content-id-put>\n\na new page version will be created once you update the content.\n\ncheers", "name": "", "is_accepted": true } ]

[ { "text": "hi [@atlassiandev](/u/atlassiandev), \ni’ve created a product issue on this, see <https://ecosystem.atlassian.net/browse/acejs-148> \ncheers, \nanne", "name": "", "is_accepted": true } ]

[ { "text": "[@daniel](/u/daniel) miraculously, it works fine now. its being invoked just once. i didn’t make any changes. don’t know what changed. thanks anyway for your help.", "name": "", "is_accepted": true } ]

[ { "text": "hi,\n\ndid you find a solution?\n\ni got it to work so far, but did not dare to use it in production …\n\nim using confluence server 7.4 lts, in my log4j.properties, there is the line:\n\nlog4j.appender.confluencelog.layout=com.atlassian.confluence.util.patternlayoutwithcontext\n\nit seems that atlassians pat…", "name": "", "is_accepted": true } ]

[ { "text": "thanks for the reply.\n\nwe managed to fix the issue by exporting the certificate from the browser and importing it to the keystore.", "name": "", "is_accepted": true } ]

[ { "text": "hi [@tbinna](/u/tbinna),\n\nthanks for bringing this to our attention. i have confirmed that we do indeed support setting the header value but a bug was causing your action not to show if you didn’t have the chrome option defined in target.options.\n\nthe fix for this should be live soon.", "name": "", "is_accepted": true } ]

[ { "text": "i may have misunderstood, but have you defined the following three contexts in your <web-resource> within the atlassian-plugin.xml file:\n\n<context>jira.view.issue</context>\n\n<context>jira.navigator.simple</context>\n\n<context>jira.navigator.advanced</context>\n\nthese contexts should be in the <web-resou…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@alvaro.aranda](/u/alvaro.aranda),\n\nwe’re aware of the issue: <https://ecosystem.atlassian.net/browse/acjira-1391>\n\ndave", "name": "", "is_accepted": true } ]

[ { "text": "hi [@improwiser.engineeri](/u/improwiser.engineeri),\n\nfor the issue of not knowing how much app data will be uploaded, we recommend using a label with each upload and at the beginning send a manifest of all the files you’ll be sending and their labels so you can track them as they come in, which is the second option that you’…", "name": "", "is_accepted": true } ]

[ { "text": "hi. we’re talking on reddit also. an example is here:\n\n[[image]](https://aws1.discourse-cdn.com/atlassiandeveloper/original/3x/6/0/60c945a295e556b958330f8e901ddd07a947d591.png \"image\")\n\ndef field = getfieldbyname(\"standards\")\n\ndef otherfield = getfieldbyname(\"other\")\n\nif(field.getvalue() == \"mycoolvalue\"){\n\notherfield.sethidden(true).setrequired(false).setformvalue(\"\")\n\n} else{\n\notherfield.sethidden(false).setrequ…", "name": "", "is_accepted": true } ]

[ { "text": "[image] markwarburton:\n\ncannot post //1/cards/{card id deleted}/attachments\n\nbased on that error, it looks like you’re trying to post to //1/cards/ instead of /1/cards/. does updating that make a difference?", "name": "", "is_accepted": true } ]

[ { "text": "not sure about the api version, but we switch the base url between releases.\n\nfor example: [app-server-1.mydomain.com](http://app-server-1.mydomain.com) for the current release, and next release might be [app-server2.mydomain.com](http://app-server2.mydomain.com).\n\nwe can host the next release of the app whoever app-server2 is, put the new version in the marketplace …", "name": "", "is_accepted": true } ]

[ { "text": "just an update on the timeline, heading should be in the next release (1.5 weeks out)", "name": "", "is_accepted": true } ]

[ { "text": "turned out to be the format issue with the json. fixed myself. thank you.", "name": "", "is_accepted": true } ]

[ { "text": "this seems to be a java issue:\n\nsolution 1: configure java 7\n\nit is need to enable tls 1.2 protocol with java property in the command line\n\nmvn -dhttps.protocols=tlsv1.2 install\n\ninstall is just an example of a goal\n\nthe same error for ant can be solved by this way\n\njava -dhttps.protocols=tlsv1.2 -…", "name": "", "is_accepted": true } ]

[ { "text": "i think you need to get the separation of frontend and backend straight. you will not be able to show any popup from java, you need to do this in javascript on the client side.", "name": "", "is_accepted": true } ]

[ { "text": "have a look at: [ace and aui 7 and 8](https://community.developer.atlassian.com/t/ace-and-aui-7-and-8/33179/2)", "name": "", "is_accepted": true } ]

[ { "text": "[@raulpelaez](/u/raulpelaez) the problem is that your are dealing with the bundling & compression logic of jira. as such it is more difficult to assume the location of the script. if you are sure that the other script is in the same location you should be able to load the file using a relative path as javascript/css…", "name": "", "is_accepted": true } ]

[ { "text": "we can detect via project type key.\n\n<https://docs.atlassian.com/software/jira/docs/api/7.6.1/com/atlassian/jira/project/type/projecttypekeys.html>\n\nproject. [getprojecttypekey](https://docs.atlassian.com/software/jira/docs/api/7.1.5/com/atlassian/jira/project/project.html#getprojecttypekey--)() = projecttypekeys. software\n\ncheers,", "name": "", "is_accepted": true } ]

[ { "text": "figured it out. searched to find documentation and there was none. great, another undocumented feature that gets activated by default! fun times! i love atlassian products so much!\n\ndisable it with the following css class on your form: ajs-dirty-warning-exempt.\n\ni found this by inspecting the search…", "name": "", "is_accepted": true } ]

[ { "text": "custom fields are back! we want to make them great again;) :blush: :rocket: :muscle: :wink:\n\nwe have finished recently work on custom filed types, custom field object type, context configuration extension point, support for forge custom fields on create issue view, and other smaller improvements. a …", "name": "", "is_accepted": true } ]

[ { "text": "i’m not aware of a way to achieve this via the cli, but you can indeed delete apps via the developer console (‘settings’ => ‘delete app’) as long as they are not in use by anyone (‘overview’ => ‘total installation count’ is 0), otherwise the deletion is refused:\n\n[image]", "name": "", "is_accepted": true } ]

[ { "text": "have you tried using the layout property? if i remind correctly using layout: basic will remove the padding and the mandatory title. see the last entry in the properties table [here](https://developer.atlassian.com/platform/forge/manifest-reference/modules/#jira-project-page).", "name": "", "is_accepted": true } ]

[ { "text": "hi all!\n\nthere is already a rate limiting mechanism in place to protect customers instances, to keep then usable. the mechanism is used for all endpoints including rest apis. our jira sres try to tune them to not harm our customers. there might be some situations when sres need to change standard th…", "name": "", "is_accepted": true } ]

[ { "text": "here’s an announcement about deprecations in july around various group related endpoints [6 new group apis and 2 group api deprecations for confluence cloud](https://community.developer.atlassian.com/t/6-new-group-apis-and-2-group-api-deprecations-for-confluence-cloud/40358)", "name": "", "is_accepted": true } ]

[ { "text": "hi [@avelit](/u/avelit), i’d suggest opening a marketplace issue in the [vendor service desk portal](https://ecosystem.atlassian.net/servicedesk/customer/portal/9/group/30)", "name": "", "is_accepted": true } ]

[ { "text": "for global end user accounts (doesn’t include service desk users), the following definitely holds:\n\natlassian user accounts are global, and their immutable identifiers are unique in the global domain of account ids. those identifiers will be reported consistently by all systems backed by atlassian a…", "name": "", "is_accepted": true } ]

[ { "text": "replying to let others know if they are having the same ‘issue’…\n\nturns out my user key was set as \"value\" and not value. this meant that the body header was being set as:\n\nbody: {\"accountid\": \"\"value\"\"}\n\nalso as a side note, my initial code block should have used:\n\nlet bodydata = `{\"accountid\": \"${…", "name": "", "is_accepted": true } ]

[ { "text": "i have found the problem\n\ni remove the add blocker named : ghostery\n\nnow it works fine …\n\nsorry for this, it was the add blocker in the end, it was working fine few month ago …\n\nthanks for helping\n\nyann", "name": "", "is_accepted": true } ]

[ { "text": "a closer look showed that parts of an older version of the plugin got cached, where tabledata was not an array…", "name": "", "is_accepted": true } ]

[ { "text": "i don’t know specifics on how/why it works the way it does.\n\nmaybe this help article shines some light on it? <https://confluence.atlassian.com/cloud/blog/2019/05/upcoming-changes-to-atlassian-account-profiles>", "name": "", "is_accepted": true } ]

[ { "text": "thanks [@julia](/u/julia),\n\ni have created [confcloud-71683](https://jira.atlassian.com/browse/confcloud-71683). i suspect the root cause is the same as [confcloud-71603](https://jira.atlassian.com/browse/confcloud-71603) so i will follow this up with the confluence team.\n\nregards,\n\ndugald", "name": "", "is_accepted": true } ]

[ { "text": "[@s1093](/u/s1093),\n\ni’m not aware of any forge modules that extend the “export word” feature; hence, there isn’t an easy way to just inject your word template. that means reproducing all the capabilities of that feature in your forge app. and, that feature is a very old feature of jira, so it’s built into jira…", "name": "", "is_accepted": true } ]

[ { "text": "[image] laszlo.cseko:\n\na found that documentation says, apps cannot access this rest resource.\n\nam i getting 401 because i am calling it from an app even if acting on behalf of admin user?\n\nthat is correct. the documentation is accurate: an app can’t use that rest api, even if it is impersonati…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@candid](/u/candid),\n\nthank you for taking the time to explain this issue so clearly. i’ve reproduced it and have consequently created <https://jira.atlassian.com/browse/confcloud-71276> for the confluence team to address.\n\nregards,\n\ndugald", "name": "", "is_accepted": true } ]

[ { "text": "hey [@cpriestley](/u/cpriestley),\n\nyou can do this by removing the schedule permission in your project’s permission scheme for everybody (except maybe admins).\n\nthis will block people from moving issues in the backlog.\n\ncheers,\n\npeter", "name": "", "is_accepted": true } ]

[ { "text": "adaptavist’s arquillian integration for atlassian products may be useful for you: [atlassian-arquillian-containers](https://bitbucket.org/adaptavist/atlassian-arquillian-containers/src)\n\nall of our integration testing is implemented with the above.", "name": "", "is_accepted": true } ]

[ { "text": "i verified that the id was indeed included in the list, but i think i figured out the issue.\n\nthe documentation lists the uri for retrieving the export status as:\n\nhttps://trello.com/1/organizations/{orgidorname}/exports/{exportid}?key={key}&token={token}\n\ni believe there is a slash missing after th…", "name": "", "is_accepted": true } ]

[ { "text": "hi marc,\n\nthe api should still work. i just tested it myself and when i had the correct username wiki/rest/api/user/bulk/migration?username=correct it returned a response with the username and accountid but when i had the wrong username wiki/rest/api/user/bulk/migration?username=wrong, the response …", "name": "", "is_accepted": true } ]

[ { "text": "[@kjacobs](/u/kjacobs),\n\nyou will need the context to specify when jira will load your javascript, for testing you can use\n\n<context>atl.general</context>\n\ni’m wondering if maybe your code is running before the page be rendered;\n\ncan you try below example?\n\najs.toinit(function() {\n\nalert('hello world')\n\n});\n\n…", "name": "", "is_accepted": true } ]

[ { "text": "it looks like either your app or one of your dependency jars (de.westlotto.jira.plugins.stmd:wlstmdimport) has been built with java 9 or newer, while version of bnd tool does not support that yet. i’d look into getting an older version of the corresponding binary or recompiling your code for java 8,…", "name": "", "is_accepted": true } ]

[ { "text": "hi,\n\ni think they readded timezone and locale again.\n\nyou can use:\n\nap.user.getlocale((locale) => { })", "name": "", "is_accepted": true } ]

[ { "text": "if someone has the same problem, i managed to get trello to update the custom fields with the following code:\n\nusing system.net.http;\n\nusing system.net.http.headers;\n\nusing system.text.json;\n\nusing system.collections;\n\nprivate static async task<string> putcustomfieldsasync(string cardid, string customf…", "name": "", "is_accepted": true } ]

[ { "text": "trellopowerup.getrestapi will give me access to client.js rest api , but i think that are actually 2 separate things, right?\n\ncorrect, client.js is separate from power-up.js and the rest client it gives you. [client.js](https://developers.trello.com/docs/clientjs) is a small, api wrapper that provides some helper methods for interacting with…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@pzvyagin](/u/pzvyagin),\n\nthanks for raising this. yes, we realised recently that removing applicationuser from overridesecurity was a wrong step. we’re now working towards fixing this in eap05.\n\nkamil", "name": "", "is_accepted": true } ]

[ { "text": "sure. i put together a sample at:\n\n<https://bitbucket.org/dwester42a/example-jira-events-with-lifecycleaware>\n\nat [bitbucket](https://bitbucket.org/dwester42a/example-jira-events-with-lifecycleaware/src/aaea4c448d27e03aa8d935132b15e37066a88df1/pom.xml?at=master&fileviewer=file-view-default#pom.xml-45) the sal-api gets imported:\n\n<dependency>\n\n<groupid>com.atlassian.sal</groupid>\n\n<artifactid>sal-api</artifactid>\n\n<version>3.0.0</version>…", "name": "", "is_accepted": true } ]

[ { "text": "i finally solved my problem.\n\ni added meta-inf/spring/plugin-context.xml, with :\n\n<?xml version=\"1.0\" encoding=\"utf-8\"?>\n\n<beans xmlns=\"http://www.springframework.org/schema/beans\"\n\nxmlns:xsi=\"http://www.w3.org/2001/xmlschema-instance\"\n\nxmlns:atlassian-scanner=\"http://www.atlassian.com/s…", "name": "", "is_accepted": true } ]

[ { "text": "you can use macro’s conversioncontext to determine if request is for display or preview and generate custom preview when necessary.\n\nprivate boolean ispreview(conversioncontext context) {\n\nreturn conversioncontextoutputtype.preview.value()\n\n.equals(context.getoutputtype());\n\n}\n\nsomething li…", "name": "", "is_accepted": true } ]

[ { "text": "if this is in the event listener then you probably should set the user in the current thread with com.atlassian.confluence.user.authenticateduserthreadlocal.set(user)\n\nhave not tried this particular api but we do this in our background threads to change the current user in the current thread. and af…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@aksagraw](/u/aksagraw) - perhaps this has something to do with your basic auth header, and not your post body. can you try to make the same api call using curl or postman? if successful, i would compare the authorization header value from those calls compared to what you’re seeing on the failed request.", "name": "", "is_accepted": true } ]

[ { "text": "i guess you could use the following endpoints from the v1.0 of the api:\n\nget all projects - /rest/api/1.0/projects [rest resources provided by: bitbucket server - rest](https://docs.atlassian.com/bitbucket-server/rest/5.16.0/bitbucket-rest.html#idm8297225296)\n\nget all repos of a project /rest/api/1.0/projects/{projectkey}/repos [rest resources provided by: bitbucket server - rest](https://docs.atlassian.com/bitbucket-server/rest/5.16.0/bitbucket-rest.html#idm8287395680)\n\nget all …", "name": "", "is_accepted": true } ]

[ { "text": "spring scanner has several pros (and a couple of cons):\n\npros\n\nthe add-on starts up a lot faster (which is the main reason for it and makes admin happier which makes atlassian happier and so forth).\n\nthe add-on code is much much cleaner - no more declaring things in the atlassian-plugin.xml - it ends…", "name": "", "is_accepted": true } ]