Datasets:

---

clips

/

mqa

like 52

Follow

CLiPS 10

[ { "text": "solved it already.\n\ni got confused by the request package and addon.httpclient.\n\nusing httpclient works the way i want it.\n\nexample:\n\nvar httpclient = addon.httpclient(req);\n\nhttpclient.get({\n\n\"headers\": {\n\n\"content-type\": \"application/json\",\n\n\"accept\":…", "name": "", "is_accepted": true } ]

[ { "text": "most likely,authenticationcontext isn’t being imported from osgi yet. each service or component that’s provided by the host application or another plugin needs to be imported from osgi. assuming you’re using atlassian-spring-scanner, the easiest way to do this is to create a simple class in your plu…", "name": "", "is_accepted": true } ]

[ { "text": "so the good news - you’re not doing anything wrong… the problem is that the contents of the dialog in that location is dynamic so webresourcemanager isn’t being called to get the tags.\n\nthe fix though is pretty simple.\n\nin your actiontestlink add:\n\n@htmlsafe\n\npublic string getscripttags()\n\n…", "name": "", "is_accepted": true } ]

[ { "text": "try replacing /current/ with /archived/ in those urls: <https://my.atlassian.com/download/feeds/archived/bitbucket.json>\n\nafter that you’ll have to parse the dates in the json file.", "name": "", "is_accepted": true } ]

[ { "text": "[@nunosantos](/u/nunosantos), having a background task to do the heavy lifting is actually a recommended practice. you can use an event listener or rely on a scheduled task (using the scheduler api). if you use the scheduler api, you will be able to make sure your background task is compatible with data center insta…", "name": "", "is_accepted": true } ]

[ { "text": "hey everyone,\n\nthanks for looking into this! it happened that there was something wrong with my cloud instance. i attempted this on a different instance and i was then able to install the app and test it out.", "name": "", "is_accepted": true } ]

[ { "text": "was worth a shot! we also have a forge app that makes page edits. i just looked up the code we use to build the request body and here it is:\n\nconst buildrequestjsonbody = (page, modifiedpagecontent) => {\n\nconst requestbody = {\n\n'type': page.content.type,\n\n'version': {\n\n'number': page.content.ver…", "name": "", "is_accepted": true } ]

[ { "text": "welcome to the atlassian developer community, [@111101](/u/111101)\n\nthere is “work in progress” about [renaming sites](https://blog.developer.atlassian.com/site-rename-feature-for-cloud-customers-an-update-for-app-vendors-faqs/) (sorry, that’s 2 years old but it’s the latest i know about). according to this page:\n\ndoes the old site url redirect to the new one?\n\nyes it does. we retain a history of all site names used by t…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@a.webster](/u/a.webster),\n\nto add an icon to the web-item on the navigation sidebar you will have to use this syntax:\n\n<web-item>\n\n<param name=\"iconclass\" value=\"aui-icon-small aui-iconfont-world\"/>\n\n</web-item>\n\nthe value provided to the iconclass param can be any css class name. in the example …", "name": "", "is_accepted": true } ]

[ { "text": "seems i can hack arround the problem 2) by setting tabindes to -1 for the rest of elements except the input i want to focus - when i close the select2 i would have do some cleaning up…here the first idea/sketch\n\n$(\"#gruppe-members-dlg-person-search\").on(\"select2-open\", function() {\n\n$(\"[tabindex=0]…", "name": "", "is_accepted": true } ]

[ { "text": "[@pawejakimiak](/u/pawejakimiak),\n\ni tried all the update verbs that i could find using [jira server api docs](https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/#adding-a-comment--examples), in the hopes the functionality hasn’t changed. here’s what i found:\n\nadd\n\nfails for both name and id with status 400 and this response:\n\n{\n\n\"errormessages\": [],\n\n\"errors\": {\n\n\"components\": \"could not fin…", "name": "", "is_accepted": true } ]

[ { "text": "you should not shut down the executorservice that is provided by the host application when your plugin is disabled/uninstalled/shut down since it’s being used by multiple plugins. the shared executorservice should only be shut down on application shutdown and bitbucket will take care of it.", "name": "", "is_accepted": true } ]

[ { "text": "hi [@maks](/u/maks)\n\nget installed plugins and find “atlassian ui plugin” plugin (key: com.atlassian.auiplugin)\n\ncheers\n\nadam", "name": "", "is_accepted": true } ]

[ { "text": "hi there!\n\ncurrently we support sizing in fixed increments for these custom ui modules, see viewportsize: <https://developer.atlassian.com/platform/forge/manifest-reference/modules/#jira-issue-panel>", "name": "", "is_accepted": true } ]

[ { "text": "class fulldiffcontentcallback extends abstractdiffcontentcallback {\n\nprivate final stringbuffer buffer;\n\npublic diffsegmenttype currentsegmenttype;\n\npublic fulldiffcontentcallback(stringbuffer buffer) {\n\nthis.buffer = buffer;\n\ncurrentsegmenttype = null;\n\n}\n\n@over…", "name": "", "is_accepted": true } ]

[ { "text": "hi ajay, i’m not aware of any immediate plans to provide this module but i will follow up with the relevant team", "name": "", "is_accepted": true } ]

[ { "text": "ok, problem solved. this problem is related about a introscope agent installed at server.", "name": "", "is_accepted": true } ]

[ { "text": "i did some research and found that this can be achieved using “web items”.", "name": "", "is_accepted": true } ]

[ { "text": "[@yannherren](/u/yannherren) welcome to the atlassian developer community.\n\nno. it is not possible to authenticate to the jira cloud rest apis using 3rd-party identity providers. developers are limited to basic, oauth, and jwt, as described in [our auth guide](https://developer.atlassian.com/developer-guide/auth/).\n\nmaybe you could explain why [oauth](https://developer.atlassian.com/cloud/jira/platform/oauth-2-3lo-apps/) wouldn’t work for your…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@zhoubingyang](/u/zhoubingyang),\n\ni will look at this.\n\nregards,\n\ndugald", "name": "", "is_accepted": true } ]

[ { "text": "this is a community. people answer as they have time and if they have the knowledge. if they don’t answer, then it would because the right knowledge hasn’t read your question and responded. atlassian answers has a more active scriptrunner community: most of the individuals in this community are add-…", "name": "", "is_accepted": true } ]

[ { "text": "hi! thanks, i have solved it myself. i will now post and share how did i do it as sadly there are almost no examples on “how to” and i spent some time то find out. you need to use pagebuilderservice and add this in java:\n\nprivate static final logger log = loggerfactory.getlogger(synchronizationschem…", "name": "", "is_accepted": true } ]

[ { "text": "try to [providing custom soy functions](https://bitbucket.org/atlassian/atlassian-soy-templates/src/master)", "name": "", "is_accepted": true } ]

[ { "text": "in short no, you get the content transformed. take a look in this class <https://docs.atlassian.com/confluence/5.8.8/com/atlassian/confluence/content/render/xhtml/formatconverter.html> it should do what you need to do", "name": "", "is_accepted": true } ]

[ { "text": "ok after some deeper research i found out that someone already had a similar issue.\n\n[parts of javascript not working in issue navigator](https://community.developer.atlassian.com/t/parts-of-javascript-not-working-in-issue-navigator/13004/9)\n\nadding this made the trick:\n\njira.bind(jira.events.issue\\_refreshed, function() {\n\n// your code\n\n});\n\nthank you [@daz](/u/daz) , you helped a lot!", "name": "", "is_accepted": true } ]

[ { "text": "hello alex,\n\nsince [create issue](https://developer.atlassian.com/cloud/jira/platform/rest/v3/?utm_source=%2fcloud%2fjira%2fplatform%2frest%2f&utm_medium=302#api-api-3-issue-post) rest api returns a json response body, you can check it out by calling something like\n\nprint dumper($issue);\n\nor check if the $issue->{key} exists, which might tell you that an issue has been successfully created. usually, the http status is checked but i am not sure …", "name": "", "is_accepted": true } ]

[ { "text": "i found the solution. to resolve the problem i updated pom.xml to declare the necessary repository. here is what i added to pom.xml within :\n\n<pluginrepositories>\n\n<pluginrepository>\n\n<id>atlassian-public</id>\n\n<url>https://packages.atlassian.com/maven-external/</url>\n\n…", "name": "", "is_accepted": true } ]

[ { "text": "do you want your dashboard to appear within the jira application? if you write an add-on for jira server, you can make your data appear within the ui framework that jira provides.\n\na) you could [write a gadget](https://developer.atlassian.com/server/jira/platform/writing-gadgets-for-jira/) or gadgets for jira’s own dashboard.\n\nb) you could [write a report](https://developer.atlassian.com/server/jira/platform/report/) that appears under ‘repor…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@manjuprem](/u/manjuprem),\n\nthe problem seems to be in your admin.js file. “import type” is flow syntax. if you are using flow, you need to add the flow preset to your babelrc.\n\nif you are using plain javascript, you cannot import or use types.", "name": "", "is_accepted": true } ]

[ { "text": "thanks for confirming [@jens](/u/jens). for the benefit of others, the solution was to change the version of node to v14.\n\ni have created <https://ecosystem.atlassian.net/browse/frge-203> to improve the documentation and/or have the forge cli enforce the use of a supported version of node.", "name": "", "is_accepted": true } ]

[ { "text": "this was totally the issue. i am a .net developer (yes there are those of us who build add-ons using .net) and visual studio likes to save files with that bom. saved the utf-8 files appropriately and it works now.\n\nto fix it a user needs to:\n\nsave the file using the save as command:\n\n[https://hasjir…](https://hasjiratestaddon030418.blob.core.windows.net/has-jira-firstaddon-assets/saveas.png)", "name": "", "is_accepted": true } ]

[ { "text": "okay, i finally figured it out.\n\nthe mistake is actually quite ridiculous.\n\nwindows 10 did not let me change to the data type i wanted.\n\ne.g. meaning i had atlassian-connect.json.txt as a type instead of atlassian-connect.json\n\nanyway, cheers\n\nchristian", "name": "", "is_accepted": true } ]

[ { "text": "seems i found the cause of the problem and solution.\n\nthe cause: when using com.atlassian.bitbucket.web.conditions.ispersonalrepositorycondition, the plugin misses com.atlassian.bitbucket.auth.authenticationcontext in meta-inf/plugin-components/imports file. authenticationcontext is used by the cond…", "name": "", "is_accepted": true } ]

[ { "text": "have you tried searching for your property in the ui as a regularly logged-in user? does searching for other fields work when you authenticate with oauth?\n\nmy suspicion is that this isn’t related to oauth, but somehow to the connect app installation. is the connect app installed properly on your tes…", "name": "", "is_accepted": true } ]

[ { "text": "in case it helps, we recently had same issue, also related with the loading of all.js file.\n\nfollowing the steps [here](https://developer.atlassian.com/cloud/jira/software/adding-a-board-configuration-page/), in step 2 the example for the hbs view includes the statement to import all.js from <https://ac-getting-started.atlassian.net/atlassian-connect/all.js>, but loading of this file was f…", "name": "", "is_accepted": true } ]

[ { "text": "in bitbucket, you can authorise resource requests by using the com.atlassian.bitbucket.user.securityservice component.\n\nwrap your request with securityservice.withpermission().call(). this way you also don’t have to impersonate a specific user like you are describing with the jiraauthenticationconte…", "name": "", "is_accepted": true } ]

[ { "text": "we have identified this issue and a fix has been merged. it will take time to be released and reach production.\n\nthe ticket we raised for this issue is here: <https://ecosystem.atlassian.net/browse/acjs-592>", "name": "", "is_accepted": true } ]

[ { "text": "dear community,\n\nmany thanks for that many responses and hints :wink:\n\ni would say: “lessons learned”. my assumption before debugging my code was, that when calling a rest endpoint, all its objects die after execution. i was wrong. :grimacing:\n\ni had a license managing class created that was called …", "name": "", "is_accepted": true } ]

[ { "text": "hi! for all future readers,\n\nthe issue was that i had included an extra “s” in my url (i.e. “[atlasssian.net](http://atlasssian.net)” instead of “[atlassian.net](http://atlassian.net)”).\n\nohhh the joys of coding !", "name": "", "is_accepted": true } ]

[ { "text": "hi,\n\nfor jira software applicationmanager.getapplication(\"jira-software\");\n\nfor service desk applicationmanager.getapplication(\"jira-servicedesk\");\n\nif the result is empty then the corresponding app is not installed.\n\ncheers", "name": "", "is_accepted": true } ]

[ { "text": "hey, if i understood you correctly that you need to save some kind of config, then yes, you have to save that. if it’s host specific and related to the plugin/app itself, you could use app properties. keep in mind it’s not for storing sensitive data and it’s 32 kb per property, so if you’re going to…", "name": "", "is_accepted": true } ]

[ { "text": "hi aatifnazar,\n\nas far as i know it is not currently possible. see the following posts:\n\n[adding issue field to project create screen with rest api](https://community.developer.atlassian.com/t/adding-issue-field-to-project-create-screen-with-rest-api/865)\n<https://community.atlassian.com/t5/jira-questions/jira-api-create-issue-with-custom-field/qaq-p/1126615>\n\nyou can create a custom field context [https://d…](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-contexts/#api-rest-api-3-field-fieldid-context-post)", "name": "", "is_accepted": true } ]

[ { "text": "hi, according to the documentation (<https://developer.atlassian.com/server/framework/atlassian-sdk/web-item-plugin-module/>) web item allow you to define new links in application menus. so it is the reason why there no current page is provided. in the definition of a web item you usually specifies w…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@rnunez](/u/rnunez) ,\n\ni’ve only observed positive integer ids, however, to be safe i’ve created [confcloud-72640](https://jira.atlassian.com/browse/confcloud-72640) so the confluence team documents the format.\n\nregards,\n\ndugald", "name": "", "is_accepted": true } ]

[ { "text": "they actually do. it’s part of the jira core api :slight\\_smile:\n\n<https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-issue-post>", "name": "", "is_accepted": true } ]

[ { "text": "you’ll want to make use of the web trigger api:\n\n<https://developer.atlassian.com/platform/forge/runtime-reference/web-trigger-api/>", "name": "", "is_accepted": true } ]

[ { "text": "it’s possible to do at that point the marketplace is just a landing page.\n\nyou can create a basic app in p2 that just has a single rest call that validated the license. cloud becomes trickier since you would have the rest call on your webspo which would then have to make the call to the server to ma…", "name": "", "is_accepted": true } ]

[ { "text": "daniel,\n\nthe httpservlet interface is designed to be streamy, so i speculate that there’s no place designed to be able to extract the sent content (or at least not more than once). and the actual object returned by confluence is obviously an implementation detail and subject to change anyway.\n\nwhat …", "name": "", "is_accepted": true } ]

[ { "text": "looks like the jql query is not url encoded. can you try using this url instead?\n\nhttps://mysite.atlassian.net/rest/api/3/search?jql=issuetype%3dvulnerability%26resolution%3dunresolved", "name": "", "is_accepted": true } ]

[ { "text": "[image] gautamsinghania95:\n\nplease see image-1 of the app setup.\n\nhello, based on this image, you used tesco as the consumer key. please update your config.properties and change oauthkey to tesco to match your configuration in jira. this mismatch is causing the status 401.", "name": "", "is_accepted": true } ]

[ { "text": "maybe it’s time to consider using subdomains instead of ports: [confluence.enevapps.com:443](http://confluence.enevapps.com:443) and [hipchat.enevapps.com:443](http://hipchat.enevapps.com:443).", "name": "", "is_accepted": true } ]

[ { "text": "question is wrong, sorry for bothering.", "name": "", "is_accepted": true } ]

[ { "text": "[@david](/u/david) when your app receives the installation lifecycle callback, the installation process has not yet completed. if your app returns an error, the installation will be rolled back. your app is granted access to the tenant’s data later on in the process.\n\nthe enabled lifecycle callback (a regular w…", "name": "", "is_accepted": true } ]

[ { "text": "ah, that’s my app. i’ll fix it up. :frowning: must have been caught by gdpr.", "name": "", "is_accepted": true } ]

[ { "text": "we asked about this in the decommissioned forge slack channel and got advise from the forge team how to deduce the site information, though it turned out to be only applicable for jira and not confluence at the time (right now you can still apply the jira approach on confluence because forge is not …", "name": "", "is_accepted": true } ]

[ { "text": "try calling the ace middleware with\n\napp.get(\"/test\", addon.authenticate(true), (req, res) => ...\n\nthis should populate addon.httpclient correctly.", "name": "", "is_accepted": true } ]

[ { "text": "finally found the problem! thanks to [@alexander.kueken](/u/alexander.kueken) example files, i knew that everything was setup properly but it still failed to load the language. turns out that passing the property file in native2ascii to transform non ascii characters into unicode-encoded ascii characters converted properl…", "name": "", "is_accepted": true } ]

[ { "text": "non-standard http/https ports are currently not supported nor are there any plans or considerations on making the change to accept non-standard ports. you are welcome to raise the feature request for this here: <https://ecosystem.atlassian.net/servicedesk/customer/portal/14/group/39/create/138>", "name": "", "is_accepted": true } ]

[ { "text": "hi [@davemeyer](/u/davemeyer) ,\n\ni believe oauth 2.0 (3lo) apps will soon be able to register and receive webhooks. according to [trello](https://trello.com/c/x3crhfna/91-jira-webhooks-3lo), this is targeted this month (june 2021).\n\nregards,\n\ndugald", "name": "", "is_accepted": true } ]

[ { "text": "hi [@alimert](/u/alimert)\n\nthis is not a representative example, but it should work\n\n<form id=\"admin\" class=\"aui\">\n\n<select id=\"select2-example2\">\n\n<option value=\"null\"> please select a project </option>\n\n#foreach( $pname in $pnames )\n\n<option value=\"$pname\"> $p…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@david2](/u/david2),\n\ni think you’ve formatted the properties incorrectly. for example, let’s say an app defines an entity property module as follows:\n\n\"jiraentityproperties\": [\n\n{\n\n\"key\": \"refapp-issue-complexity\",\n\n\"name\": {\n\n\"value\": \"issue complexity\"\n\n},\n\n\"entitytype\": \"issue\",\n\n\"ke…", "name": "", "is_accepted": true } ]

[ { "text": "i think in this case, the weight only applies to the registered panels. the extension point starts after the built in fields, but it will order all panels based on weight.\n\nunfortunately, the documentation is not entirely clear on this because they chose to reuse the generic\n\nweight attribute docume…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@maguspereira](/u/maguspereira)\n\natlassian is providing design resources for figma at [figma - @atlassian](https://www.figma.com/@atlassian) . they are not specifically for ui kit, but since it follows the [atlassian design guidelines](https://atlassian.design), you should be good to use them anyway.", "name": "", "is_accepted": true } ]

[ { "text": "if there is a package entity in your rest component (in the atlassian-plugin.xml) try removing it. this solved the exact same issue for me. if omitted, the whole plugin will be scanned for resources.", "name": "", "is_accepted": true } ]

[ { "text": "[@i05](/u/i05) we’ve released @forge/[email protected] with the fix for this issue. please let us know if this does not solve the problem you are facing!", "name": "", "is_accepted": true } ]

[ { "text": "i managed to solve it. the problem is that the schema settings object for juggling db has different variables than the one in config.json.\n\nhere is a correct settings-object (which is the “store” object in config.json) example:\n\n{\n\n“type”: “$db\\_type”,\n\n“host”: “$db\\_url”,\n\n“username”:\"$db\\_usr\",\n\n“pas…", "name": "", "is_accepted": true } ]

[ { "text": "for a single select custom field, the value you set is the id of the option, not its value. here’s how the option id and option value are retrieved from a custom field option:\n\n/**\n\n* the id of the option or null if it currently does not have one.\n\n*\n\n* @return the id of the option or null if it doe…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@ejobbers](/u/ejobbers),\n\ni think that using prerepositoryhookcommitcallback is a good start. the oncommitadded method will be called with each commit. from there you can call out to the scmservice or the commitservice depending on what details you need. it sounds like you only need the file names, in which ca…", "name": "", "is_accepted": true } ]

[ { "text": "do atlas-mvn eclipse:eclipse before importing if you cant see the plugin in the import panel", "name": "", "is_accepted": true } ]

[ { "text": "[@danielwester](/u/danielwester) that’s correct, it’s because of the wildcard in “images”. the message is displayed to the user so that all the app’s permissions are transparent to them, allowing them to decide if they want to accept or not. we don’t want the user unknowingly accepting permissions that they don’t actu…", "name": "", "is_accepted": true } ]

[ { "text": "i managed to solve this and thought i’d post a reply here in case it helps anyone else with a similar problem.\n\nan error was being reported in the build log, but wasn’t apparently severe enough to prevent it working on my dev machine (even with a clean and rebuild).\n\ni ran the build with the -z swit…", "name": "", "is_accepted": true } ]

[ { "text": "solution:\n\ni actually have the wrong, untransformed atlassian-plugin.xml in my target/ directory,\n\nit is because i have upgraded webpack,\n\n…and the copywebpackplugin doesn’t accept my “ignore” instruction, as highlighted by [this stackoverflow post](https://stackoverflow.com/a/62172723), so it overrides the normal atlassian-plugin.xml.", "name": "", "is_accepted": true } ]

[ { "text": "atlassian’s pocketknife querydsl module abstracts the activeobjects “features” and helps a lot. we are using ao only to manage the database schema (table creation, migrations), everything else is done with querydsl.\n\nyou can find the pocketknife source code here: [atlassian-pocketknife-querydsl](https://bitbucket.org/atlassian/atlassian-pocketknife-querydsl/src/master/)\n\nthe …", "name": "", "is_accepted": true } ]

[ { "text": "hi [@jens](/u/jens),\n\ni don’t think this change will necessitate manual upgrade approvals. from memory, the changes that require approvals are:\n\nchange of payment model\n\nincrease of scopes\n\nchange of baseurl.\n\nregards,\n\ndugald\n\ncc [@chparker](/u/chparker)", "name": "", "is_accepted": true } ]

[ { "text": "i kinda solved this by using a workaround. this did not give me real dynamic functionality, but i was able to fit the solution to my needs.\n\nso what i basically did was to bind an autocomplete event to the field i was trying to listen to. when filled my javascript would add checkboxes, in my case, t…", "name": "", "is_accepted": true } ]

[ { "text": "yes, apps timeout after 10 seconds. see [invocation limits](https://developer.atlassian.com/platform/forge/platform-quotas-and-limits/).\n\nthere isn’t currently any way to increase the timeout or background a request.", "name": "", "is_accepted": true } ]

[ { "text": "[@xcodinglabs](/u/xcodinglabs) the app icons are once again woking. thank you for your patience.", "name": "", "is_accepted": true } ]

[ { "text": "i created a new plugin from scratch with the sdk and merged step by step code and configuration items from my original project. the root cause was this meta-inf/spring/plugin-context.xml:\n\n<?xml version=\"1.0\" encoding=\"utf-8\"?>\n\n<beans xmlns=\"http://www.springframework.org/schema/beans\"\n\nxmlns:…", "name": "", "is_accepted": true } ]

[ { "text": "this problem looks like to be fixed.\n\nthe new version of my add-on has been created automatically since 24/apr/2017.", "name": "", "is_accepted": true } ]

[ { "text": "[@criley](/u/criley): connect is the name of the framework which allows developers to create apps for atlassian cloud products. it consists of a javascript api (ap), the very important atlassian-connect.json descriptor file (in which you define your integration points) and a set of jwt/oauth security rules that …", "name": "", "is_accepted": true } ]

[ { "text": "could you tell me the exact dependency which brings in com.atlassian.jira.transaction\n\nas i am facing this error when i compile\n\n[error] test/src/main/java/com/test/jira/app/service/dbmanagerimpl.java:[10,38] package com.atlassian.jira.transaction does not exist\n\nanswer\n\ni got my answer by just putt…", "name": "", "is_accepted": true } ]

[ { "text": "you’re not doing anything wrong. it looks like jira cloud is limiting their support for languages to:\n\nru-ru: translations for the “ru-ru” (russian) locale.\n\nde-de: translations for the “de-de” (german) locale.\n\npt-pt: translations for the “pt-pt” (portuguese) locale.\n\nen-us: translations for the “…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@jbolufer](/u/jbolufer) ,\n\ni think what’s happening here is that your user, although it can see the project settings, is not a member of a project role or group where administer projects permission has been granted to (refer to the blue box in the image below). in which case, the rest api is returning the corr…", "name": "", "is_accepted": true } ]

[ { "text": "this is a how-to. see question for the answer.", "name": "", "is_accepted": true } ]

[ { "text": "hi [@jbevan](/u/jbevan) ,\n\nthanks for reporting this. i’ve reproduced the error and created [confcloud-72639](https://jira.atlassian.com/browse/confcloud-72639).\n\nregards,\n\ndugald", "name": "", "is_accepted": true } ]

[ { "text": "in my experiments, there is no dynamic value as i think you’re wanting. the value that gets displayed is the property as set on the issue. what ever you set to status will be displayed.\n\nthe following code worked for me to set the status of a glance.\n\nap.request({\n\ntype:'put',\n\nurl:'/rest/api/2/i…", "name": "", "is_accepted": true } ]

[ { "text": "running the command ‘atlas-clean’ will remove the target directory and the application. running atlas-run again will set it up again.", "name": "", "is_accepted": true } ]

[ { "text": "found jira\\_expressions, they seem a bit simpler:\n\n\"conditions\": [\n\n{\n\n\"condition\": \"jira\\_expression\",\n\n\"params\": {\n\n\"expression\":\"['[system] change'].includes(issue.issuetype.name)\"\n\n}\n\n…", "name": "", "is_accepted": true } ]

[ { "text": "take a look at [this atlassian-plugin.xml](https://bitbucket.org/resah/confluence-macro-tutorial/src/208497acc40f0ddc16e9ae4f57b004e8db180588/src/main/resources/atlassian-plugin.xml?at=default&fileviewer=file-view-default#atlassian-plugin.xml-70)…\n\n…with the following xhtml-macro:\n\n<xhtml-macro name=\"box\" class=\"com.example.plugin.confluence.boxmacro\"\n\nkey=\"box-xhtml\"\n\nicon=\"/download/resources/com.example.plugin.confluence.macromagic/images/64x64\\_package.png\">\n\n...\n\n<!-- additional…", "name": "", "is_accepted": true } ]

[ { "text": "ok after spending the entire weekend trying to get to the bottom of this and trying other alternatives like forward, pagekite, beame-insta-ssl, [portmap.io](http://portmap.io), yaler, openport… i have managed to work out that it is google app engine endpoints that are causing me the problem. normal communication with s…", "name": "", "is_accepted": true } ]

[ { "text": "[[image]](https://aws1.discourse-cdn.com/atlassiandeveloper/original/3x/b/8/b887abd45bbcd419c14798f4f6e3c3d94151f4a0.png \"image\")\n\n<meta name=\"decorator\" content=\"atl.admin\"/>\n\n<meta name=\"admin.active.section\" content=\"atl.jira.proj.config\"/>\n\n<meta name=\"admin.active.tab\" content=\"item\\_tracker\\_project\\_admin\\_link\"/>\n\n<meta name=\"project\" content=\"${projectkey}\"/>\n\n<meta name=\"projectkey\" content=\"${pr…", "name": "", "is_accepted": true } ]

[ { "text": "did you add the [read scope](https://developer.atlassian.com/cloud/jira/platform/scopes/) for your add-on? i believe that it is required even for read operations.", "name": "", "is_accepted": true } ]

[ { "text": "hi anne,\n\nthe format of atlassioan-connect.json is wrong.\n\nmy config file is\n\n{\n\n“scopes”:[\n\n“read”,\n\n“write”,\n\n“act\\_as\\_user”\n\n],\n\n“vendor”: {\n\n“name”: “my app”,\n\n“url”: “<https://mywebsite.com>”\n\n},\n\n“description”:“this is my description”,\n\n“key”:“testing.io.jira”,\n\n“lifecycle”:{\n\n“uninstalled”:\"/ji…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@esedofredrick](/u/esedofredrick), take a look at <https://developer.atlassian.com/platform/forge/build-a-custom-ui-app-in-confluence/>", "name": "", "is_accepted": true } ]

[ { "text": "[@david.pinn](/u/david.pinn), just to add to ivan’s reply, you can see the full scope of our opt-in mechanism with the jql query [project = ac and text ~ “when opted in by apps”](https://ecosystem.atlassian.net/issues/?jql=project%20%3d%20ac%20and%20text%20~%20%22when%20opted%20in%20by%20apps%22).\n\nthree issues are yet to be completed:\n\n[ac-2425](https://ecosystem.atlassian.net/browse/ac-2425) remove support for oauth 2 jwts with user keys as the sub claim when opted in by apps\n\n[ac…](https://ecosystem.atlassian.net/browse/ac-2433)", "name": "", "is_accepted": true } ]

[ { "text": "if you can’t access that topic you can request access through this jsd: <https://ecosystem.atlassian.net/servicedesk/customer/portal/9/create/147>\n\njust create a ticket and we’ll take care of it.", "name": "", "is_accepted": true } ]

[ { "text": "hey [@tbinna](/u/tbinna) - can you share the ticket number for your top vendor submission, i’m having trouble tracking it down.\n\ncheers,\n\nchris", "name": "", "is_accepted": true } ]

[ { "text": "juste resolved by adding the katl-commun.jar to the plugin project.", "name": "", "is_accepted": true } ]

[ { "text": "you can totally use the atlassian cache api in both data center and server.\n\nthere is general documentation about it here: <https://developer.atlassian.com/server/confluence/atlassian-cache-2-overview/>\n\nand there is specific detail on how it behaves on data center under the caches subheading here: [ht…](https://developer.atlassian.com/server/jira/platform/developing-for-high-availability-and-clustering/)", "name": "", "is_accepted": true } ]

[ { "text": "that should be searchrequestservice and searchrequestmanager respectively.\n\n<https://docs.atlassian.com/software/jira/docs/api/latest/com/atlassian/jira/issue/search/searchrequestmanager.html>\n[https://docs.atlassian.com/software/jira/docs/api/latest/com/atlassian/jira/bc/filter/searchrequestservice.h…](https://docs.atlassian.com/software/jira/docs/api/latest/com/atlassian/jira/bc/filter/searchrequestservice.html)", "name": "", "is_accepted": true } ]