Datasets:

---

clips

/

mqa

like 52

Follow

CLiPS 10

[ { "text": "welcome! it looks like the countdown power-up stores its data in the shared scope on a card. this is accessible via the plugindata on a card. you can access this via 1/cards/{idcard}/plugindata1 documented here: <https://developers.trello.com/reference#cardsidplugindata>.\n\nhere is an example of the re…", "name": "", "is_accepted": true } ]

[ { "text": "hey, just to let you know we released both [@atlassian/i18n-properties-loader](https://www.npmjs.com/package/@atlassian/i18n-properties-loader) and [@atlassian/wrm-react-i18n](https://www.npmjs.com/package/@atlassian/wrm-react-i18n) packages today that have a fixed node compatibility and are compatible with node 10+.\n\nlet me know in case you have any other issues.", "name": "", "is_accepted": true } ]

[ { "text": "can you pass the user as a parameter into your new thread and use the jiraauthenticationcontext#setloggedinuser(applicationuser) method to set the user context on that thread?\n\nportfolio has permissions and you have to be in the group defined under portfolio permissions in order to retrieve values, …", "name": "", "is_accepted": true } ]

[ { "text": "is docker running? :sweat\\_smile:\n\nran into something similar yesterday and realized i wasn’t actually running docker…", "name": "", "is_accepted": true } ]

[ { "text": "your best bet is going to be making a power-up that draws/manages its own checklist items and their data. there isn’t a clean way to keep extra data about checklist items alongside the checklist items. the checklist items really only support the normal rest methods to add/update them.", "name": "", "is_accepted": true } ]

[ { "text": "[@ovalet](/u/ovalet), neither of these identifiers have a publicly documented format, and these differences should not impact the functioning of your app. consider raising bug reports for the issues you’ve seen.", "name": "", "is_accepted": true } ]

[ { "text": "hi [@boyter](/u/boyter),\n\nunfortunately there is no such functionality available. bitbucket webhooks offer retries to cover for the occasional network glitch or brief downtime. they are not a suitable means for your use case.\n\ni would suggest that you look into building a separate service which will be listening…", "name": "", "is_accepted": true } ]

[ { "text": "one solution here: <https://codesandbox.io/s/atlaskitbutton-buttongroup-with-icon-broken-eqj6x>\n\nbasically:\n\nfor element that you want to grow to fit (in your case the left hand text element), remove “display:100%” and add “flex-grow:1”\n\ni think the button is expanding after the first render, and the…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@kchan](/u/kchan),\n\nthanks for your reply. in the meantime i was able to fix the issue by myself. i used the code snippet from one of the example apps to get the selected text. this one worked for me:\n\nconst { extensioncontext, contentid } = useproductcontext();\n\nlet selectedtext;\n\nif (iscontextmenuexten…", "name": "", "is_accepted": true } ]

[ { "text": "we have tried with hash tag approach in our app and it worked for us.\n\nhttps://{domain}.atlassian.net/plugins/servlet/ac/{key}/app-entry?project.key=demo&project.id=10000#!/manage/{newpage}\n\nconstructor(props) {\n\nsuper(props);\n\nif (window.ap) {\n\nwindow.ap.getlocation(location => {\n\n…", "name": "", "is_accepted": true } ]

[ { "text": "[@michal.nykiel](/u/michal.nykiel) being whitelisted means that the assets field will get associated with service desk projects automatically without an admin having to manually go through the screen schemes. please fill out this form to be whitelisted: <https://forms.gle/rh4ffkqntetpkunj9>", "name": "", "is_accepted": true } ]

[ { "text": "we already have this in the backlog: <https://ecosystem.atlassian.net/browse/acjira-1849>", "name": "", "is_accepted": true } ]

[ { "text": "after digging a bit deeper in the documentation i could find this\n\nfor convenience, any of the resources that require a {servicedeskid} path parameter also accepts other identifiers.\n\nfor example, if a servicedesk(id: 15) corresponds to a project(id: 10012, key: abc) , then issuing a request to…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@masterkeylog](/u/masterkeylog)!\n\nunder the hood, aui uses a jquery plugin called “tablesorter” to provide the sorting behaviour. specifically, aui uses [v2.17.7 of mottie’s fork of tablesorter](https://github.com/mottie/tablesorter/tree/v2.17.7).\n\naccording to [the docs of the modded tablesorter plugin](https://mottie.github.io/tablesorter/docs/), you can cause the table to re-sort itself by doing the following…", "name": "", "is_accepted": true } ]

[ { "text": "maybe you could use the /rest/servicedeskapi/servicedesk/{servicedeskid}/customer end-point. specification is [here](https://developer.atlassian.com/cloud/jira/service-desk/rest/#api-servicedesk-servicedeskid-customer-get).\n\nthere’s a /rest/servicedeskapi/servicedesk end-point that will [return you a list of all service desks](https://developer.atlassian.com/cloud/jira/service-desk/rest/#api-servicedesk-get).", "name": "", "is_accepted": true } ]

[ { "text": "hi [@david.pinn](/u/david.pinn),\n\nthanks for posting this. i understand and am sympathetic to your view. i believe many of the recent changes were unavoidable to ensure our apis and frameworks are secure and respect the privacy of our customers. going forward, however, if there are changes that could be introduced …", "name": "", "is_accepted": true } ]

[ { "text": "hi [@clouless](/u/clouless), thank you very very much for your kindly help. i really appreciate it.\n\nafter a long time debugging, i realize that i miss the line \"homepage\": \".\" in my react package.json file, as atlassian already documented in the [custom ui](https://developer.atlassian.com/platform/forge/custom-ui/#accessing-static-assets) page.\n\n[[image]](https://aws1.discourse-cdn.com/atlassiandeveloper/original/3x/d/b/db9e0b50359586a00b5adfe425a993098be02095.png \"image\")\n\ni think we misunderstood each other becau…", "name": "", "is_accepted": true } ]

[ { "text": "my guess is that the pluginlicensemanager isn’t available on the agent (there isn’t a backing db for it to query for the licenses). you’ll need to look at something like the pre-build module (forgive me - my bamboo skills are slightly rusty - i believe that there is a better module). [https://www.go2…](https://www.go2group.com/blog/sharing-information-from-bamboo-server-to-bamboo-remote-agent/)", "name": "", "is_accepted": true } ]

[ { "text": "hi [@yvesriel](https://community.developer.atlassian.com/u/yvesriel) and [@k.menshov](https://community.developer.atlassian.com/u/k.menshov) ,\n\nthanks for bringing this to our notice.\n\nregarding the endpoint, in the case that the custom field is a multi-line text field, you are required to provide an atlassian document (see the atlassian document format: [https://developer.atlassian.com/cloud/jira/platform/a…](https://developer.atlassian.com/cloud/jira/platform/apis/document/structure)", "name": "", "is_accepted": true } ]

[ { "text": "i managed to find the answers. for the servicedeskid you use the ‘id’.\n\nyou can indeed add either a user or customer to the servicedesk. doesn’t matter if the accounttype is ‘atlassian’ or ‘customer’.\n\njust need to add the ‘accountid’ and it will work", "name": "", "is_accepted": true } ]

[ { "text": "thanks for confirming that [@hendrikschneider](/u/hendrikschneider). from my own testing, i suspected the change of bodytype from rich-text to plain-text would make a difference, but i’m not sure why. you may be able to avoid changing back to rich-text if your macro view could be generated from the macro parameters rather…", "name": "", "is_accepted": true } ]

[ { "text": "[@ofirnir](/u/ofirnir) we recognize this is a concern and we are working on an update to the app installation process whereby the initial install can be verified as coming from atlassian.\n\nwe will use the apimigrations mechanism we have used for other changes (e.g. gdpr, qsh, etc) to allow apps to opt into these …", "name": "", "is_accepted": true } ]

[ { "text": "you could potentially listen to com.atlassian.jira.event.issue.link.remoteissuelinkdeleteevent, and re-create the deleted links that you don’t want deleted. not sure that’s a good user experience.\n\nalternatively, your add-on could check for the existence of particular links upon presentation of the …", "name": "", "is_accepted": true } ]

[ { "text": "having a self-signed certificate kinda messes the entire “trust” thing out. the only one that knows that the certificate is trustworthy is you… and since forge doesn’t have a way for us to import private keys - it doesn’t have a way to verify that the certificate is you and not a bad actor.\n\nwhy not…", "name": "", "is_accepted": true } ]

[ { "text": "hey [@madamczak](/u/madamczak)\n\nplease note i asked for extension points in the listings. this is not available. i worked around this by using a javascript listener. this seems to behave properly but is of course not as nice as if an extensionpoint existed.\n\nsee attached the addition of the archived lozenge.\n\n[[01-…](https://aws1.discourse-cdn.com/atlassiandeveloper/original/3x/e/2/e227b0b5b3e8c917bd35a1ef6305cbfdf21daedf.jpeg \"01-repository-list\")", "name": "", "is_accepted": true } ]

[ { "text": "hi [@evmorov](/u/evmorov),\n\n[these](https://developer.atlassian.com/cloud/jira/service-desk/rest/#fieldformats) are the available field formats you can update. i have not yet tried setting the priority, but i think you can, you just need to see the values and how you should be forming your json.\n\nwhat i could suggest is, but this more of a hack than a solution:\n\ninvoke the /rest/api/lates…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@rosy.salame](/u/rosy.salame),\n\ncould you try explicitly adding com.atlassian.plugins.atlassian-plugins-webresource-rest:web-resource-manager as a dependency in your web-resource entry? i think that’s technically also necessary on jira and confluence, but something else just pulls that in by default.\n\ncheers,\n\nto…", "name": "", "is_accepted": true } ]

[ { "text": "hello everyone. so, we’ve been engaged with the prod/eng team, and the new change date for this api method (introducing the 409 error code) has been moved to may 4, 2020. the blog post has been updated to reflect this date change.", "name": "", "is_accepted": true } ]

[ { "text": "i’ve managed to find a “fix” for this (or at least an acceptable workaround for my purposes):\n\nyou must specify the link in one of the following forms:\n\nhttp://localhost:8090/pages/viewpage.action?spacekey=testspace&title=test+page&testparam=foo\n\nor\n\nhttp://localhost:8090/pages/viewpage.action?pagei…", "name": "", "is_accepted": true } ]

[ { "text": "you can add ?expand=names to that url and you’ll get a map of all of the fields to their field names. :slight\\_smile:", "name": "", "is_accepted": true } ]

[ { "text": "hi [@ferllarom](/u/ferllarom),\n\nhosted data storage is only available for jira and confluence cloud not for bitbucket cloud.\n\nso you’ll need to use your own data storage.", "name": "", "is_accepted": true } ]

[ { "text": "i found an alternative by using /rest/api/content/search together with container={id} as part of the cql expression. interestingly container is not mentioned as search field [here](https://developer.atlassian.com/cloud/confluence/advanced-searching-using-cql/).", "name": "", "is_accepted": true } ]

[ { "text": "is there a way to quickly experiment with updates as they would happen via the marketplace?\n\nnot sure. i think the best thing would be through a private listing with a different url and then use access token to install things.\n\nare there templates or best practices for deployment of a connect app…", "name": "", "is_accepted": true } ]

[ { "text": "hi ludek,\n\nmy solution:\n\nthe problem was, that the cloud macros are using <https://ngrok.io/> as a reverse proxy:\n\nlocal tunnel established at https://b4f0188a**.ngrok.io**/\n\ncheck http://127.0.0.1:4040 for tunnel status\n\nregistering add-on...\n\nget /atlassian-connect.json 200 12.760 ms - 633\n\nand our fir…", "name": "", "is_accepted": true } ]

[ { "text": "nope. we’re limited to the static descriptor entry.", "name": "", "is_accepted": true } ]

[ { "text": "hi [@iragudo](/u/iragudo),\n\nthanks for the hint. i used your steps to work it up from scratch. finally got to the cause of the issue i was facing while comparing. and it’s rather lame :frowning:\n\ni had a method in one of the classes with just '@path(“something”) ’ and no @get/[@post](/u/post). i deleted that “@path” in my o…", "name": "", "is_accepted": true } ]

[ { "text": "so the api is also documented here: <https://developer.atlassian.com/platform/app-migration/rest/api-group-status-api/#api-progress-transferid-post> and it appears to have the correct information and a valid example:\n\n{\n\n\"progressstatus\": \"in\\_progress\",\n\n\"percent\": 183,\n\n\"statusmessage\": \"<string>\"…", "name": "", "is_accepted": true } ]

[ { "text": "i assume you’re referring to [the /rest/api/1.0/projects/{projectkey}/repos/{repositoryslug}/pull-requests/{pullrequestid}/changes](https://developer.atlassian.com/static/rest/bitbucket-server/4.14.4/bitbucket-rest.html#idm46478324997488) call.\n\nindividual file tracking is both performed and stored on the browser. the backend isn’t involved at all, so that is unavailable from the rest api. the “unreviewed”…", "name": "", "is_accepted": true } ]

[ { "text": "i did not try with all possible solutions yet.\n\nbut if the problem happens as you describe, i think the best solution is that you do the condition checking within your javascript code, and only hide elements if those conditions are passed.\n\nthis is the simplest way as well.\n\nconst projectkey = jira.…", "name": "", "is_accepted": true } ]

[ { "text": "then you are looking for scheduling jobs ->\n\n<https://developer.atlassian.com/confdev/confluence-plugin-guide/confluence-plugin-module-types/job-module>\n\nwhich is combined with\n\n<https://developer.atlassian.com/confdev/confluence-plugin-guide/confluence-plugin-module-types/trigger-module>", "name": "", "is_accepted": true } ]

[ { "text": "after some investigations, i find the solution:\n\nvar initgetprojects = function(resturl) {\n\nvar templateprojectsselection = jira.templates.ijp.getprojects();\n\nvar auiprojectselectoptions = {\n\n/*minimuminputlength: 3,*/\n\nminimumresultsforsearch: 30,\n\nplaceholder: 'select project',\n\naja…", "name": "", "is_accepted": true } ]

[ { "text": "change:\n\n<dependency>\n\n<groupid>com.atlassian.activeobjects</groupid>\n\n<artifactid>activeobjects-core</artifactid>\n\n<version>1.4.0</version>\n\n</dependency>\n\n<dependency>\n\n<groupid>net.java.dev.activeobjects</groupid>\n\n<art…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@andy.ennamorato](/u/andy.ennamorato),\n\nwe don’t currently support ip whitelisting in atlassian cloud. you can get updates about this feature request here: [cloud-2636](https://jira.atlassian.com/browse/cloud-2636)\n\ncheers,\n\ndave", "name": "", "is_accepted": true } ]

[ { "text": "found the right context variable:\n\nyou can use $req.contextpath to include the context path.\n\nlike normal for jira server, you had to go through 7000 pages, community posts and legacy documentation to end up with [this confluence documentation](https://developer.atlassian.com/server/confluence/confluence-objects-accessible-from-velocity/) that provides the right hints. :roll\\_eyes:…", "name": "", "is_accepted": true } ]

[ { "text": "hey [@dchouksey89](/u/dchouksey89) - the 30 day trial is mandatory, you can’t work around this i’m afraid.\n\nthe two listing approach simply involves having a stripped down free version of the app, and then in app adds/notes pointing towards the fully featured one. here’s an example of a lite version of an app, there’…", "name": "", "is_accepted": true } ]

[ { "text": "[@harrybanda](/u/harrybanda), yes this should be possible.\n\nyou can use webtriggers, although be aware that these do not have authentication or authorization by default. you will want to consider that when creating your solution.\n\n<https://developer.atlassian.com/platform/forge/events-reference/web-trigger/>", "name": "", "is_accepted": true } ]

[ { "text": "hey david,\n\ni just posted an announcement on the google group.\n\nwe will be retiring the google group in 2 weeks and keep it as a read-only archive from then on.", "name": "", "is_accepted": true } ]

[ { "text": "don’t have the details to share yet; however, this was some type of change that was rolled out, and it’s since been rolled back. thanks to the thinktilt team for helping zero in on this.", "name": "", "is_accepted": true } ]

[ { "text": "no that’s not possible. keep in mind that atlaskit is written for the internal teams at atlassian so the example you see in the spotlight docs to show a spotlight next to a webitem is not possible.\n\nas an app, you can only use a spotlight component in a web panel. one thing you might want to consi…", "name": "", "is_accepted": true } ]

[ { "text": "after discussing this issue with james on a zoom call, i now understand the cause. it’s simply that i have been calling gateway.getcloudfeedback(transferid) after the transfer has completed. it turns out that getcloudfeedback should only be called before a terminating event, signaled by the cloud se…", "name": "", "is_accepted": true } ]

[ { "text": "i think fastdev was deprecated/removed:\n\n<https://developer.atlassian.com/server/framework/atlassian-sdk/automatic-plugin-reinstallation-with-fastdev/>\n\nis there still a way to run integration tests using some kind of test console?\n\nyes, but not using historic frameworks.\n\nwe use a support framewor…", "name": "", "is_accepted": true } ]

[ { "text": "so i finally found it.\n\n<https://docs.atlassian.com/atlassian-confluence/latest-server/com/atlassian/confluence/core/custompagesettingsmanager.html>", "name": "", "is_accepted": true } ]

[ { "text": "i ended up doing some digging in the confluence source code and found out that this is something that is done when activating the editor. tinymce uses it to scroll to the correct place on the page i think.\n\ni guess what i could do is mimic the behaviour of that method instead of triggering the edit …", "name": "", "is_accepted": true } ]

[ { "text": "[image] exta:\n\nis it somehow possible to disable the maven tests till use them globally?\n\nby doing atlas-run -dskiptests=true as you did.\n\n[image] exta:\n\nhere can i find the error-log, or what can cause this?\n\nthe output of atlas-run should contain the cause. otherwise you are looking for c…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@m.abdel-mola](/u/m.abdel-mola),\n\nlooked through the java api for various utilities and formatters, i stumbled to [jiradurationutils](https://docs.atlassian.com/jira/7.1.6/com/atlassian/jira/util/jiradurationutils.html) class. you can find more [here](https://docs.atlassian.com/jira/7.1.6/index.html?com/atlassian/jira/datetime/jiradurationutil.html) thought it might help. let me know if id did :slight\\_smile:\n\nthanks!\n\ncheers,\n\nanne calantog", "name": "", "is_accepted": true } ]

[ { "text": "hi,\n\nyou need to use userservice:\n\nuserservice userservice = componentaccessor.getcomponent(userservice.class);\n\napplicationuser updateuser = userservice.newuserbuilder(applicationuser).emailaddress(\"newemail\").name(\"newname\").build();\n\nuserservice.updateuservalidationresult validationresult = userser…", "name": "", "is_accepted": true } ]

[ { "text": "so, i found another post that fixed my issues.\n\nneed to add this to web resource:\n\ncom.atlassian.auiplugin:tabs\n\nfunny how it was documented as being included and did not need this in previous versions. now they have taken it out and we have to include it specifically.\n\natlassian this is something y…", "name": "", "is_accepted": true } ]

[ { "text": "list<string> issuetypeids = immutablelist.<string>builder()\n\n.addall(getissuetypeids(issuetypescheme))\n\n.add(mynewissuetype.getid())\n\n.build();\n\nissuetypeschememanager.update(issuetypescheme, issuetypeids);", "name": "", "is_accepted": true } ]

[ { "text": "hello [@noreez.ulhassanshah](/u/noreez.ulhassanshah),\n\nsince usage of passwords in basic auth is being deprecated (see [acjira-1465](https://ecosystem.atlassian.net/browse/acjira-1465)), have you tried using basic email:apitoken for authentication?\n\ncheers,\n\nian", "name": "", "is_accepted": true } ]

[ { "text": "hi [@franciscogomezbalast](/u/franciscogomezbalast),\n\nfrom <https://bitbucket.org/atlassian/atlassian-spring-scanner/src/master/> it says that @scanned was removed. other vendors opted for @named , see [here](https://community.developer.atlassian.com/t/where-are-the-annotations-in-atlassian-spring-scanner-2-0/31539).\n\ncheers,\n\nanne", "name": "", "is_accepted": true } ]

[ { "text": "keep it simple, i reckon. something like this:\n\nap.request({\n\nurl: url,\n\ntype: 'get',\n\nsuccess: function(text) {\n\ndosuccesstuff();\n\n},\n\nerror: function(xhr, statustext) {\n\ndofailurestuff();\n\n}\n\n});", "name": "", "is_accepted": true } ]

[ { "text": "hi [@rhysdiab](/u/rhysdiab)\n\nthis is introduced recently and we are going to announce in next few days. this change has been put in place to prevent any user confusion between locally installed apps and apps installed from atlassian marketplace.\n\nto resolve this, you will now need to use a separate instance to und…", "name": "", "is_accepted": true } ]

[ { "text": "i had missed the npm run build before deploying to production :roll\\_eyes:", "name": "", "is_accepted": true } ]

[ { "text": "why don’t you just allow all urls?\n\npermissions:\n\nexternal:\n\nfetch:\n\nclient:\n\n- '*'\n\nthis is totally acceptable and recommended, and it shows up like this to your end users in the consent screen:\n\n[[image]](https://aws1.discourse-cdn.com/atlassiandeveloper/original/3x/d/3/d3921df33d30fb284d195f461802537bc73ded65.png \"image\")", "name": "", "is_accepted": true } ]

[ { "text": "i could not find it in the external roadmap: [ecosystem roadmap for developers](https://community.developer.atlassian.com/t/ecosystem-roadmap-for-developers/40696)\n\nbut we are actively working on this feature (ping [@nir](/u/nir) ) and it should be shipped before the end of the year.\n\nwhich oauth provider would you want to integrate against?", "name": "", "is_accepted": true } ]

[ { "text": "hi [@jordanglassman](/u/jordanglassman),\n\nit is possible to re-assign the ownership of an app, but you would have to create a [developer service desk](https://ecosystem.atlassian.net/servicedesk/customer/portal/14) ticket to trigger us. our backlog contains a project to provide team ownership of apps, but it has not been scheduled yet.\n\nregards,\n\ndugald", "name": "", "is_accepted": true } ]

[ { "text": "hi [@bugget\\_jr](/u/bugget_jr),\n\na single push can contain commits from multiple authors. are you looking at getting the authors of the commits or the user who performed the push? the authentication context should give you the author who performed the push.\n\nas for why the authentication context didn’t change when y…", "name": "", "is_accepted": true } ]

[ { "text": "i have found a solution to this problem i used this ( /wiki/rest/api/content/{contentid}?expand=body.atlas\\_doc\\_format ). in the “atlas\\_doc\\_format” i was able to retrieve the body of the wiki document and what it contains.", "name": "", "is_accepted": true } ]

[ { "text": "your assumptions about webhook behavior are correct. the server doesn’t need to actively register the webhooks, you can also define them (statically) in the atlassian-connect.json.\n\nto my knowledge, there’s not a big difference between the spring java library and the node.js ace library. they are me…", "name": "", "is_accepted": true } ]

[ { "text": "hmmm we should have thought of that first [@remie](/u/remie) :smiley: using this short snippet:\n\nrequire([\"jira/editor/customizer\"], function (customizer) {\n\ncustomizer.customizesettings(function(tinymcesettings, tinymce, schemabuilder) {\n\ntinymcesettings.plugins.push(\"directionality\");\n\ntinymcesettings.di…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@aravindviswanathan](/u/aravindviswanathan),\n\nare you creating a confluence macro, a confluence plugin, or are you directly editing confluence’s source files?\n\nthe contexts in confluence you’ll want to affect are preview, then probably both page and blogpost. the most common way to cause your code (including the aui tab…", "name": "", "is_accepted": true } ]

[ { "text": "so i understand that your problem is to find the correct user who shall be used when your scheduled jobs starts, correct?\n\ni don’t know if is a “elegant” way but you could save the username of the administrator who installed the plugin after installation and before scheduling your jobs using active …", "name": "", "is_accepted": true } ]

[ { "text": "to be honest, i gave up on connect sizing the iframe correctly, so we have this snippet to fix it:\n\n// fix for incorrect iframe sizing\n\nexport const resizefix = (): void => {\n\nlet scrollheight = document.body.scrollheight;\n\nconst observer = new mutationobserver(() => {\n\nif (scrollheight !== do…", "name": "", "is_accepted": true } ]

[ { "text": "hi adam,\n\nif i’m not mistaken, ms sql is not really supported out of the box – you will need to do some manual work and write your own storage adapter as mentioned in this thread:\n\n[image]\n\n[depreciation warning for ace with postgres](https://community.developer.atlassian.com/t/depreciation-warning-for-ace-with-postgres/36866) [atlassian developer tools](/c/atlassian-developer-tools)\n\nhi,\n\nwhen using…", "name": "", "is_accepted": true } ]

[ { "text": "i figured it out. looking at the handlemessage method, i realized one of the parameters was javax.mail.message, which has a reference to the containing folder. since i’m copying the message to a child folder (in this case, inbox/debug), i could simply use javamail components to get the child folder,…", "name": "", "is_accepted": true } ]

[ { "text": "after a good amount of trials i was able to copy an attachment from a blogpost to another using the rest api using the following script:\n\ndef attid = 'att457998341'\n\ndef att = unirest.get('/wiki/rest/api/content/' + attid).asobject(map).body\n\ndef downloadurl = '/wiki' + att['\\_links']['download']\n\ndef …", "name": "", "is_accepted": true } ]

[ { "text": "there is a ‘developer support’ option on the upper-right hand side of this very page.", "name": "", "is_accepted": true } ]

[ { "text": "here is an answerd (i got everything work now):\n\npublic class loadadmin extends confluenceactionsupport implements beanable {\n\n// some code here\n\n}\n\npublic object getbean()\n\n{\n\njsonobject json = new jsonobject()\n\n.setproperty(\"tasks\", tasks)\n\n.setproperty(\"totalcount\", …", "name": "", "is_accepted": true } ]

[ { "text": "it got solved. please refer to below link:\n\n[image]\n\n[how to create issue without logged in user](https://community.developer.atlassian.com/t/how-to-create-issue-without-logged-in-user/4841/14?u=dchouksey89) [jira server](/c/jira/jira-server)\n\nhi [@david.pinn](/u/david.pinn) & [@daniel](/u/daniel),\n\ni got the solution. i need to pass basic authentication of jira user in header of third party api client then i can able to get logged in u…", "name": "", "is_accepted": true } ]

[ { "text": "hello, [@mabo](/u/mabo),\n\nfirst off, loading an issue with new issue(id) is an expensive operation on its own, so you will be able to load at most 10 in one expression. add to that issue property access and you end up with a limit of 9 issues and 1 property, or 8 issues and 2 properties, and so on.\n\nthe way j…", "name": "", "is_accepted": true } ]

[ { "text": "couple of ways of doing it. the easiest would be to do an web-resource module that just targets atl.general. this will then be loaded on every page. at that point you can pretty much do whatever you want (in your case - take a look at the jira.events object in page (there’s some documentation somewh…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@tbinna](/u/tbinna),\n\ni created a similar issue for this, see: [jracloud-69718](https://jira.atlassian.com/browse/jracloud-69718). i also answered you in the developer support ticket.\n\ncheers,\n\nanne calantog", "name": "", "is_accepted": true } ]

[ { "text": "[image] mawi:\n\nnull for uri: <https://hostxxxx/rest/api/content/1185808839/child/page?next=true&limit=25&start=25>\n\nin this error message you’re not including the whole base url https://hostxxx/wiki you’re missing the context /wiki\n\ni’m just making sure this isn’t the problem before pinging the e…", "name": "", "is_accepted": true } ]

[ { "text": "i haven’t dug into it much, but my guess is that sitemesh is confused. try removing the html, head and body tags from your view template. ie:\n\n<head>\n\n</head>\n\n<body>\n\n<p>say 'hallo': $entry</p>\n\n</body>\n\n</html>\n\nshould be\n\n<p>say 'hallo': $entry</p>\n\ni suspect things will work after tha…", "name": "", "is_accepted": true } ]

[ { "text": "upon further debugging i found the fetch arguments where not properly cleared between 2 calls. this caused the payload to move from request tot request. as long as it where posts, the payload was overwritten and there was no problem. at the next get however, the payload was not cleared.\n\nso my bad. …", "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": "i see we aren’t providing guidelines just yet in design.atlassian and jira has not updated settings pages yet, so it’s difficult to anticipate the way the navigation should work. sorry about that.\n\ni generally expect users to collapse the navigation which will improve the existing ui a bit. it’s not…", "name": "", "is_accepted": true } ]

[ { "text": "so, after asking someone from atlassian, this behaviour of savemacro is intended and there is a ticket to somehow mitigate this issue with content properties: <https://jira.atlassian.com/browse/confcloud-65437>", "name": "", "is_accepted": true } ]

[ { "text": "overriding the validate method in the report class is what i did now. not the best solution, but it works.", "name": "", "is_accepted": true } ]

[ { "text": "ok,\n\nso after doing the exact same steps from [disable velocity caching](https://developer.atlassian.com/server/confluence/disable-velocity-caching/) did the trick for me. i don’t know why it didn’t work the first time, but it looks fine now. the topic can be closed :slight\\_smile:", "name": "", "is_accepted": true } ]

[ { "text": "thank you for all the feedback.", "name": "", "is_accepted": true } ]

[ { "text": "it used to be, but that rest end point was (and should have been) blacklisted. if you need to send email you’ll need to do it on your own. there are a couple of sass providers out there that have api’s if you don’t want to do it all yourself (mailchimp is one that comes to mind).", "name": "", "is_accepted": true } ]

[ { "text": "this should now be resolved", "name": "", "is_accepted": true } ]

[ { "text": "atlassian contacted me and explained everything. case closed =)", "name": "", "is_accepted": true } ]

[ { "text": "for anyone else who went through this problem -\n\ni used below link to rectify the above problem based on last error.\n\n[[jean]](https://stackoverflow.com/users/2255784/jean)\n[slf4j error: class loader have different class objects for the type](https://stackoverflow.com/questions/29504180/slf4j-error-class-loader-have-different-class-objects-for-the-type)\n\njava, tomcat, slf4j\n\nasked by\n\n[jean](https://stackoverflow.com/users/2255784/jean)\n\non [01:09am - 08 apr 15 utc](https://stackoverflow.com/questions/29504180/slf4j-error-class-loader-have-different-class-objects-for-the-type)\n\n…", "name": "", "is_accepted": true } ]

[ { "text": "for those who may be interested:\n\nwe are now using the confluence app [vendor sales report](https://marketplace.atlassian.com/apps/1211117/vendor-sales-reports?hosting=server&tab=overview) which cannot only notify us of new sales, but also provides input for charts that can give interesting insights. it’s free and open source, so open to improvements from anyone. very recommendable!", "name": "", "is_accepted": true } ]

[ { "text": "hi [@gyngyikiss](/u/gyngyikiss),\n\nunfortunately, it is not possible to live update rendered forge apps using product events. yet. but we have similar features that enable live updates on our roadmap.\n\nthanks,\n\nvitalii", "name": "", "is_accepted": true } ]

[ { "text": "you’ll need to implement something like atlaskit (react based - <https://atlaskit.atlassian.com>) or aui ( straight html - <https://aui.atlassian.com> ) or build your own using the guidelines at <https://design.atlassian.com>", "name": "", "is_accepted": true } ]

[ { "text": "what type of module are you doing? if you’re doing a page - you can specify the sizetoparent attribute. see <https://developer.atlassian.com/cloud/jira/platform/about-the-javascript-api/> for more details.", "name": "", "is_accepted": true } ]

[ { "text": "dear flowyoe,\n\nnow i see where you are coming from. although the name is similar a page property macro does not store content properties. it is just a table with data.\n\nwhat you have to do is parse the content of the page in storage format and extract your properties out of it. atlassian’s page prop…", "name": "", "is_accepted": true } ]