Datasets:

---

clips

/

mqa

like 52

Follow

CLiPS 10

[ { "text": "hi [@patrick](/u/patrick),\n\nyou can modify your descriptor so that your project page is passed the id of the board. to do this, add the board.id [context parameter](https://developer.atlassian.com/cloud/jira/platform/context-parameters/). your descriptor will then look as follows:\n\n\"jiraprojectpages\": [{\n\n\"key\": \"collect-feedback\",\n\n\"name\": {\n\n\"value\": \"sprint feedback\"\n\n},\n\n\"u…", "name": "", "is_accepted": true } ]

[ { "text": "we’ve already seen such problem a couple of times. we have learned that if there is a problem with the billing, the ability to install apps is disabled. atlassian is aware of this problem", "name": "", "is_accepted": true } ]

[ { "text": "i’m not german but found out that zitat should be preisangebot :slight\\_smile:\n\nblame the english language which has such double-meaning words as “quote”.", "name": "", "is_accepted": true } ]

[ { "text": "hi [@epalardy](/u/epalardy),\n\ni have not encountered your exact problem, but ran into similar ones occasionally. you might want to try wrapping your code in an explicit transaction using sal’s transaction template - see [brydie’s answer to a similar issue for details.](https://community.atlassian.com/t5/answers-developer-questions/hibernateexception-could-not-initialize-proxy-the-owning-session/qaq-p/556473#m94129)\n\ncheers,\n\nhenrik", "name": "", "is_accepted": true } ]

[ { "text": "earlier this year atlassian moved cloud customers to an atlassian account. we’ve discovered some painpoints in that move specifically with calling rest api endpoints with basic authentication.\n\nread this page for further details [https://confluence.atlassian.com/cloud/the-upgrade-to-atlassian-accoun…](https://confluence.atlassian.com/cloud/the-upgrade-to-atlassian-account-873871204.html)", "name": "", "is_accepted": true } ]

[ { "text": "one of the key “features” of connect is that you as a vendor are responsible for the hosting of the app. you can use any service you want.\n\nmany vendors choose for aws or heroku, we are using google cloud (firebase). you can use leaseweb.\n\nthe point of the questionnaire is not to force you to use aw…", "name": "", "is_accepted": true } ]

[ { "text": "okay, final update: i have it!\n\nthe final problems i was having, above, were because my fixture for creating pages wasn’t clearing things out properly before the spacemanager removed the space. that’s what was leading to that final hibernate error: a page that was still in the session somewhere woul…", "name": "", "is_accepted": true } ]

[ { "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>. \nhere is an example of the re…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@rosy.salame](/u/rosy.salame) -\n\nif your app is private on the marketplace, it should take no time at all. on your cloud instance, an admin can enable private listings to install these non-public apps.\n\nif your app is private, it’s listing/descriptor isn’t published anywhere. to install the app, you would use upl…", "name": "", "is_accepted": true } ]

[ { "text": "the issue was i was using my admin credentials. you need to create another set of credentials and authenticate using those.", "name": "", "is_accepted": true } ]

[ { "text": "hi [@alj](/u/alj) - there is an api; however, the docs are not published on [developer.atlassian.com](http://developer.atlassian.com). if you’re a jira align customer, you can navigate to the in-product api docs here:\n\n<https://yourinstance.net/api-docs/public/>", "name": "", "is_accepted": true } ]

[ { "text": "i’ll answer my own question as a colleague helped me solve it:\n\ni had to edit c:\\applications\\atlassian\\atlassian-plugin-sdk-6.3.4\\apache-maven-3.2.1\\conf\\settings.xml\n\nand uncomment the “localrepository” tag from:\n\n<!-- localrepository\n\n| the path to the local repository maven will use to store…", "name": "", "is_accepted": true } ]

[ { "text": "i think your best option at this point would be to implement a user picker that customers can use to find the right accountid.\n\nhowever, there is no user picker rest api in confluence cloud - it has been requested here <https://jira.atlassian.com/browse/confcloud-59705> (that ticket has a partial work…", "name": "", "is_accepted": true } ]

[ { "text": "the api in 1 is not an api for jira, it’s for the jira rest client, which is an application that runs outside jira and talks to it over rest, reproducing some of the data structures in jira so you’re not working with plain raw rest formatted data.\n\nthe api in 2 is for plain jira, and in 3, there’s a…", "name": "", "is_accepted": true } ]

[ { "text": "how are you selecting the issues? could you be retrieving non jsw issues?", "name": "", "is_accepted": true } ]

[ { "text": "hi [@clouless](/u/clouless), it looks like there is a new version 11.0.3 of the breadcrumbs package: [unpkg - @atlaskit/breadcrumbs](https://unpkg.com/browse/@atlaskit/[email protected]/changelog.md)\n\nmaybe you can try to check if the update solves your problem.\n\nthanks,\n\nmaciej", "name": "", "is_accepted": true } ]

[ { "text": "thanks to your code, some huge coincidence and a lot of jira source code debugging i have been able to solve the original issue with the workflowtransitionservice :slight\\_smile:\n\nwhen i tried to add your code, there was an exception telling me, that there already exists a draft for this particular w…", "name": "", "is_accepted": true } ]

[ { "text": "that link goes to the cloud docs, this is server.\n\nthis api does not seem to exist on server, however you could use the applinks manifest available on baseurl/rest/applinks/1.0/manifest, e.g. <https://confluence.atlassian.com/rest/applinks/1.0/manifest> (btw [@rmassaioli](/u/rmassaioli) your confluence is a bit outdat…", "name": "", "is_accepted": true } ]

[ { "text": "hey! try adding a content-type header to specify that the data is json:\n\n-h 'content-type: application/json'", "name": "", "is_accepted": true } ]

[ { "text": "while i don’t know exactly what fixed the issue, i just noticed that the latest release of atlaskit now works with tree-shaking. i now get minimal artifacts with everything shared from atlaskit in a big vendor.js.\n\nmagic! :heart\\_eyes:\n\n[[screen shot on 2018-09-14 at 11:00:35]](https://aws1.discourse-cdn.com/atlassiandeveloper/original/3x/f/1/f16097df59c25b9fd0899811987243475ba1c232.jpg \"screen shot on 2018-09-14 at 11:00:35\")", "name": "", "is_accepted": true } ]

[ { "text": "hi [@justinarias](/u/justinarias),\n\ni have a few thoughts:\n\ndoes your app have write scope?\n\ni note you have given permissions to all users and adding attachments is enabled, but have you tried this with a curl command as shown in the docs since the 403 indicates a permission problem. ap.request acts with the permiss…", "name": "", "is_accepted": true } ]

[ { "text": "hi @alexanderpiotnikov this page will guide you on how to do this programmatically yourself. it’s a two step process so read the instructions carefully. i did this on an add-on i was writing and it was amazing how much more efficient it made building it out.\n\n[https://developer.atlassian.com/market…](https://developer.atlassian.com/market/faqs/installing-an-add-on)", "name": "", "is_accepted": true } ]

[ { "text": "hi,\n\nwhat’s the response once the task has finished running (changed status from running to complete)? note that the api returns a redirect to the status of the async task that it starts. in the end, the result should show a summary of all issues that were affected and those that couldn’t because of…", "name": "", "is_accepted": true } ]

[ { "text": "looking at the json data transferred from the browser, it adds a “:1” to the customfield id to set the child. so assuming that your customfield id is 10302 then you should try:\n\nissueparams.addcustomfieldvalue(\"customfield\\_10302:1\", childoptionid);\n\njust compute the proper string from customfield id…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@nhac.tat.nguyen](/u/nhac.tat.nguyen) ,\n\ni haven’t used this in a while but i’ll give it a shot :slight\\_smile: i believe issue has a field called issuelinks which contains an array of links or link objects. if you want to filter by link name, [issuelinks](https://docs.idalko.com/exalate/display/ed/issuelinks) has a linkname field of type string or you can also use linktype …", "name": "", "is_accepted": true } ]

[ { "text": "hi [@kkutter](/u/kkutter),\n\ncan you provide a little more context as to what your goals are?\n\nconfluence makes aui’s buttons available through their product. since aui 7.2, aui’s buttons are styled with an alpha-transparent background colour so that they appear on light grey backgrounds.\n\ncheck this codepen: [http…](https://codepen.io/chrisdarroch/pen/wkeyga)", "name": "", "is_accepted": true } ]

[ { "text": "hi [@evmorov](/u/evmorov),\n\napologies, these posts might have been in lost. nevertheless, i will be looking at your questions and see what i can do.\n\ncheers,\n\nanne calantog", "name": "", "is_accepted": true } ]

[ { "text": "hi [@andreas1](/u/andreas1),\n\nthis seems like a bug in atlassian-connect-spring-boot.\n\nper [spring mvc 3.2 preview: making a controller method asynchronous](https://spring.io/blog/2012/05/10/spring-mvc-3-2-preview-making-a-controller-method-asynchronous/), there are three threads involved in processing of an async request in servlet 3:\n\nhandling the request and starting concurrent processing\n\ninvoking the handler…", "name": "", "is_accepted": true } ]

[ { "text": "in case someone has the same issue in the future, this is the solution:\n\n// inject this\n\n// import com.atlassian.jira.timezone.timezonemanager;\n\ndatetimeformatter formatter = datetimeformatter.ofpattern(\"yyyy-mm-dd hh:mm\");\n\n// get timezone of the current logged in user\n\ntimezone timezone = timezonema…", "name": "", "is_accepted": true } ]

[ { "text": "see <https://blog.developer.atlassian.com/change-notice-padding-update-for-jira-cloud-navigation-ui/>", "name": "", "is_accepted": true } ]

[ { "text": "hi [@gabrieludvar](/u/gabrieludvar),\n\nyou run into a typical problem when using scripted fields that access the search index. this reindex will work without any problems if it is a background index. in this case, the search index is available and searching for issues works as expected.\n\nin the case that you have a loc…", "name": "", "is_accepted": true } ]

[ { "text": "that’s best for atlassian to answer of course, and i’ve been about to ask about the following observation for quite a while, but at least it partially explains the difference for us:\n\napparently depending on whether or not your app requires user permissions, any installation into jira or confluence …", "name": "", "is_accepted": true } ]

[ { "text": "unfortunately bitbucket is in the middle of an upgrade of its connect js currently. that change is partially done and some of that partial work is leaking out. the most correct thing to do currently is:\n\nap.require('messages', function (messages) {\n\nmessages.error();\n\n});\n\nsee: [https://developer.a…](https://developer.atlassian.com/cloud/bitbucket/jsapi/messages/)", "name": "", "is_accepted": true } ]

[ { "text": "hi [@charlie](/u/charlie), [@mdoar](/u/mdoar) and [@danielwester](/u/danielwester),\n\nmy understanding is that the email went out prematurely which is why there hasn’t been an announcement in this forum yet. would you mind waiting until the team has posted the announcement because that should answer most questions.\n\nregards,\n\ndugald", "name": "", "is_accepted": true } ]

[ { "text": "welcome to the atlassian developer community [@mertturkoglu](/u/mertturkoglu),\n\ni spun up a new instance of windows server 2019. i was able to install nodejs, atlas-connect, and start a new project. when i ran npm install for that project, it worked fine. i think we would need to know more about your environment, in o…", "name": "", "is_accepted": true } ]

[ { "text": "i finally found the problem. the clue was this little line:\n\ncaused by: java.lang.illegalargumentexception: invalid version number: version number may be negative or greater than 255\n\nit turned out that the confluence plugins only run on java 8 with version numbers bellow 255 (for whatever reason).", "name": "", "is_accepted": true } ]

[ { "text": "i see. as you already may have guessed, that’s a different part of the api and can’t be done while creating an issue. it requires a different set of permissions. and this part is undergoing a bit of [recent change](https://community.developer.atlassian.com/t/jira-cloud-extensibility-update-feb-2021-a-review-and-sneak-peek-into-the-future/45284). as such, you’ll find both deprecated endpoints and new experimental ones.\n\nin your cas…", "name": "", "is_accepted": true } ]

[ { "text": "you can put the “atlassian-plugin” module as a child module, not the top-parent one. for example, given the following folder structure (that would correspond to module parent-child relation):\n\nprojectroot/pom.xml <-- <packaging>pom</packaging>\n\nprojectroot/theplugin/pom.xml…", "name": "", "is_accepted": true } ]

[ { "text": "jira support replied to me to use defaultrendermanager to get altassianwikirender. then initialization is then moved to the platform.\n\nworks both for <7.6 and 7.6.x\n\n//imports\n\nimport com.atlassian.jira.issue.fields.renderer.jirarendererplugin;\n\nimport com.atlassian.jira.issue.fields.renderer.wiki.atl…", "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": "it’s in milliseconds.", "name": "", "is_accepted": true } ]

[ { "text": "hi [@odinson](/u/odinson),\n\ncan you please confirm if the project you are unable to receive events from has any restrictions on it? currently, forge apps are only able to access events from jira projects or confluence spaces that are accessible by the default user group. [https://developer.atlassian.com/platform/f…](https://developer.atlassian.com/platform/forge/events-reference/)", "name": "", "is_accepted": true } ]

[ { "text": "your confusion about the api was legit and i have noted this down as an example where documentation was confusing. for your use case, you can use [edit issue api](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-put), in which you can mention custom fields, their values and is compatible with connect apps.", "name": "", "is_accepted": true } ]

[ { "text": "make sure the base url is the same as to what you’re accessing things to. try disabling collaborative editing to see if that fixes it.\n\nfor more ideas:\n\n<https://confluence.atlassian.com/confkb/unable-to-edit-any-pages-in-confluence-6-x-due-to-collaborative-editing-867362716.html>\n\notherwise, any erro…", "name": "", "is_accepted": true } ]

[ { "text": "i think you found my ticket and i have responded to the questions i got there\n\nta\n\nmartin", "name": "", "is_accepted": true } ]

[ { "text": "hi,\n\nyou can set the following system properties when starting your confluence with the sdk:\n\n<atlassian.darkfeature.site-wide.synchrony.opt-in.disable>true</atlassian.darkfeature.site-wide.synchrony.opt-in.disable>\n\n<atlassian.darkfeature.site-wide.shared-drafts.disable>true</atlassian.darkfeature.s…", "name": "", "is_accepted": true } ]

[ { "text": "hey [@scott\\_selberg](/u/scott_selberg)\n\ni am a part of the confluence server dev team and i have identified this as a regression in 7.0.1 that we will hopefully fix in upcoming releases. you can track the progress in this ticket:\n\n<https://jira.atlassian.com/browse/confserver-59031>\n\nthank you very much for the enquiry …", "name": "", "is_accepted": true } ]

[ { "text": "i found what the problem was,\n\ni looked at the logs and could see the below\n\n“[info] [talledlocalcontainer] 2018-05-03 13:30:07,737 error [localhost-startstop-1] [bamboopluginutils] a problem has occurred when instantiating action class [isode.robot.robotreport], skipping action [viewrobotreport]\n\n[…", "name": "", "is_accepted": true } ]

[ { "text": "turns out the issue was something i thought i’d dealt with, but really hadn’t. the issue was the /installed endpoint in the end; as you can see in the descriptor, i had defined the lifecycle endpoint as \"installed\" instead of \"/installed\", so the response was never being received.\n\nchanging that lin…", "name": "", "is_accepted": true } ]

[ { "text": "from within the context of an issue, you can use this (it’s from a groovy script, may need translating into java)\n\ncustomfield buildfromfield = customfieldmanager.getcustomfieldobjects(issue)find {it.name == fieldnametolist}\n\nfieldconfig optionsfieldconfig = buildfromfield.getrelevantconfig(issue)\n\nop…", "name": "", "is_accepted": true } ]

[ { "text": "the actual response of the endpoint is 303 with a redirect, as you can see in your app. it’s just that postman is automatically following it.\n\nread more about this here: [asynchronous operations](https://developer.atlassian.com/cloud/jira/platform/rest/v2/#async-operations).", "name": "", "is_accepted": true } ]

[ { "text": "according to the docs \" the value of the request body must be a [valid](http://tools.ietf.org/html/rfc4627), non-empty json blob. the maximum length is 32768 characters.\"\n\nso i would just post the js object", "name": "", "is_accepted": true } ]

[ { "text": "i would have assumed that you could use cql to search for all content with that macro: <https://developer.atlassian.com/cloud/confluence/advanced-searching-using-cql/#macro>\n\nbut i’ll have to double check what identifier you should use for a forge app macro.", "name": "", "is_accepted": true } ]

[ { "text": "wrote my own ui to show issue key and summary details in action page.", "name": "", "is_accepted": true } ]

[ { "text": "i believe this might be because you are attempting to access activeobjects before the add-on has been fully initialized. check out [my answer to a similar question](https://community.developer.atlassian.com/t/how-to-create-custom-filed-on-start-of-plugin/9921/2?u=david.pinn); it applies to your situation too.", "name": "", "is_accepted": true } ]

[ { "text": "it’s possible that you are attempting to access components too early in the add-on lifecycle. under [plugin system events](https://developer.atlassian.com/jiradev/jira-platform/building-jira-add-ons/jira-plugins2-overview/jira-plugin-lifecycle#jirapluginlifecycle-pluginsystemevents), in the jira plugins2 overview, there’s this:\n\n“due to the shortcomings of the component initialisation stage, a listener on the pluginenabledevent is the earliest time that you …", "name": "", "is_accepted": true } ]

[ { "text": "i finally found out, why the api wasn’t working.\n\ni checked my package.json. and there you are somehow the version of my api didn’t seem to be right.\n\nchanged them to newest version.\n\n\"dependencies\": {\n\n\"@forge/api\": \"^1.2.0\",\n\n\"@forge/ui\": \"^0.13.1\"", "name": "", "is_accepted": true } ]

[ { "text": "hi [@piskunovigorm](/u/piskunovigorm) it’s not possible to get binary date with ap.request, see <https://ecosystem.atlassian.net/browse/acjira-2379>", "name": "", "is_accepted": true } ]

[ { "text": "not sure how you’re testing, but there really isn’t any magic when it comes to confluence/jira cloud installations. if you’re trying to do integration testing, you can just trigger the installation hook yourself with your own secrets and then start generating the jwt tokens. as long as your qsh and …", "name": "", "is_accepted": true } ]

[ { "text": "so can we get support for these issues or are we just up a shit creek?", "name": "", "is_accepted": true } ]

[ { "text": "i found the working solution. project permissions works only on project related module in jira. it will not work in general page\n\n\"modules\": {\n\n\"generalpages\": [\n\n{\n\n\"location\": \"system.top.navigation.bar\",\n\n\"weight\": 50,\n\n\"name\": {\n\n\"value\": \"my report\"\n\n},\n\n\"key\": \"index-pa…", "name": "", "is_accepted": true } ]

[ { "text": "hi heiko,\n\ni faced the same problem when i built the user profile settings for my confluence app. my approach was to use the existing user settings pages as a template, make a copy of one of the user settings velocity pages, and adapt this according to my needs.\n\nso if you have access to the conflue…", "name": "", "is_accepted": true } ]

[ { "text": "[@kjacobs](/u/kjacobs) ah yes, many features of the host products are actually loaded asynchronously. as such, executing code on load may get you stuck in a race condition.\n\nif you want to resolve this, you will have to determine which element you require to be available and create logic to wait for this element …", "name": "", "is_accepted": true } ]

[ { "text": "hi [@vpelizza](/u/vpelizza),\n\nyou’ll be interested to know that jira server is moving to a new look and feel more in keeping with the adg: [coming soon: updated look and feel for jira server](https://community.developer.atlassian.com/t/coming-soon-updated-look-and-feel-for-jira-server/16603). confluence server and bitbucket server are also adopting this aesthetic as well.\n\nyou’ll also be interested to know that th…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@fadli.abdulrahman](/u/fadli.abdulrahman),\n\n[image] fadli.abdulrahman:\n\nonstartappmigration stop working when disabling feature flag com.atlassian.jira.migration.app-migration.feature in jira server.\n\nin short, this is expected behaviour.\n\napp migration in both ccma and jcma is in eap and so app migration isn’t av…", "name": "", "is_accepted": true } ]

[ { "text": "if anyone ever need this, i’ve solved it by using a jira expression to check for customerrequest.requesttype.id, but doubly negated so you get a boolean otherwise it will resolve to false.\n\nlooks like:\n\n\"params\": {\n\n\"expression\": \"!!customerrequest.requesttype.id\"\n\n}", "name": "", "is_accepted": true } ]

[ { "text": "hey bill, there are some small things that aren’t correct\n\none of them is the url, this should contain /browse like in your curl example which you don’t have in your java example, so this results in a 404.\n\nalso the content-type should not be ‘application/json’ but multipart.\n\nto see the exact reque…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@adamhraban](/u/adamhraban),\n\nare you using one of the two atlassian connect frameworks ([spring boot](https://bitbucket.org/atlassian/atlassian-connect-spring-boot/src/master/) or [express](https://bitbucket.org/atlassian/atlassian-connect-express/src/master/))? if yes, this is handled automatically for you. if you’re building your own custom solution you’ll need to implement life cycle endpoints by yourself.\n\ncheers,\n\nsven", "name": "", "is_accepted": true } ]

[ { "text": "hey [@yvesriel](/u/yvesriel)\n\nthis is resolved.\n\nthanks\n\nharsh", "name": "", "is_accepted": true } ]

[ { "text": "one helpful thing is that you can include [context parameters](https://developer.atlassian.com/cloud/jira/platform/context-parameters/) in your urls: path parameters and query string parameters. those parameters can include information about the permissions that the user has, populated by jira cloud itself. if the jwt from jira validates correctly, then you know that infor…", "name": "", "is_accepted": true } ]

[ { "text": "thanks for help.\n\nin the end i found a solution. multiselect customfield edit.vm\n\nedit.vm\n\n<form class= \"aui\">\n\n<select class=\"select2-example\" id=\"select2-example\" name=\"select2-example\" multiple=\"\">\n\n<option value=\"conf\">confluence</option>\n\n<option value=\"jir…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@111112](/u/111112) ,\n\nthere’s no api allowing you to get dom elements and this is not the kind of api we’d be supporting. instead, we’d offer api’s that have a higher level of abstraction since they are easier to support and trust. for example, setcontentwatermark(message), but i think even this would likel…", "name": "", "is_accepted": true } ]

[ { "text": "the rule is much simpler: if your add-on descriptor declares a glance, all right-hand panels are ignored in the new issue view.", "name": "", "is_accepted": true } ]

[ { "text": "just use the following condition on the webhook:\n\nissuetype = epic\n\njust for information, all epics will have the same issue type id (10004) on your system, but not neccessarily others’ systems.", "name": "", "is_accepted": true } ]

[ { "text": "[@nkemjikagwacham](/u/nkemjikagwacham) feel free to use ui kit or custom ui as your app needs! there is no restriction.", "name": "", "is_accepted": true } ]

[ { "text": "thanks for following-up, [@iragudo](/u/iragudo)!\n\nthe issue was a result of the “request type” not being set when i was creating test requests via the jira admin/agent panel. add the request type to the ticket manually (or creating a ticket from the portal) resolved the issue and i was able to view the approval r…", "name": "", "is_accepted": true } ]

[ { "text": "dear benjamin,\n\nas far as i know the editor2 format is only used by atlassian. i assume you want to create a page which uses the new editor. if yes you have to set property editor: { value:“v2”} when creating the page.\n\ni copied two lines of code form our app which might help:\n\nbody: { storage: { va…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@romygreenfield](/u/romygreenfield) - i’ve reached out to the customer advocates team. you’re all set. please be sure to log and use products at least once per 120 days.\n\nsee: [https://confluence.atlassian.com/cloud/track-storage-and-move-data-across-products-873871366.html#trackstorageandmovedataacrossproducts-whath…](https://confluence.atlassian.com/cloud/track-storage-and-move-data-across-products-873871366.html#trackstorageandmovedataacrossproducts-whathappenstofreeplanproductsifthey'reinactivefortoolong)", "name": "", "is_accepted": true } ]

[ { "text": "[@niklasgrossmann](/u/niklasgrossmann) you can refer following link\n\n[image]\n\n[kitchen duty plugin for atlassian jira® by comsysto reply](https://comsysto.github.io/kitchen-duty-plugin-for-atlassian-jira/tutorial/04-step-01-planning-page--webwork-action-and-html-view/)\n\nan interactive tutorial on how to write plugins for atlassian jira® by comsysto reply\n\nyou can find sample code on following link\n\n[https://bitbucket.…](https://bitbucket.org/mdoar/webwork-sample/src/master/src/main/resources/atlassian-plugin.xml)", "name": "", "is_accepted": true } ]

[ { "text": "so i was able to sort out this issue with my colleague. basically his app id was included in the manifest-template.yml which must have caused confusion within the app. once i deleted his app id and replaced it with the app id i got in my manifest.yml after running ‘forge register’, the environment v…", "name": "", "is_accepted": true } ]

[ { "text": "i solved it. you can type the jira installation id that appears by typing the forge install:list command.\n\nthis link is described in the usage section on [readme.md](https://bitbucket.org/atlassian/forge-issue-alerting/src/master/readme.md).", "name": "", "is_accepted": true } ]

[ { "text": "it should be exported as\n\n@exportasservice(pluginupgradetask.class)", "name": "", "is_accepted": true } ]

[ { "text": "to anyone wondering, if you come across this. the problem was with the uuid of the reviewers i put the wrong id. i put the account\\_id that you received from the endpoint /user/{username} but you have to put in the uuid, i mistakenly thought they were the same thing.", "name": "", "is_accepted": true } ]

[ { "text": "#set($x = $listtwo.add($xchilds))", "name": "", "is_accepted": true } ]

[ { "text": "may be related to the change made in [action required: atlassian connect vulnerability allows bypass of app qsh verification via context jwts - #4 by remie](https://community.developer.atlassian.com/t/action-required-atlassian-connect-vulnerability-allows-bypass-of-app-qsh-verification-via-context-jwts/47072/4)\n\ntry to add @contextjwt annotation to all internal apis", "name": "", "is_accepted": true } ]

[ { "text": "hi [@jdawson](/u/jdawson), [@jack](/u/jack), [@nnmatveev](/u/nnmatveev), apologies for not being as responsive with updates and answering your questions as quickly as i would like. i am going to be working on this moving forward, but please know that we are reading these and very much appreciate your feedback & comments!\n\nand now for the u…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@andre.rodrigues](/u/andre.rodrigues),\n\ni went to the last connect week in austin and the guys from atlassian basically said it is not possible to do it. currently, there is no api for this.\n\nlet’s wait for the next episodes :slight\\_smile:", "name": "", "is_accepted": true } ]

[ { "text": "thanks for the feedback and links to more details.\n\nwill check it out.", "name": "", "is_accepted": true } ]

[ { "text": "unfortunately this [delete user api](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-user-delete) doesn’t support oauth [which is what asuser() and asapp() use for authentication](https://developer.atlassian.com/platform/forge/security/#oauth-scopes)\n\nin the rest api only those that are marked with “oauth scopes required” will work via that mechanism, e.g., [create issue api](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post) has\n\noauth scopes required: write:jira-work", "name": "", "is_accepted": true } ]

[ { "text": "hey [@ray](/u/ray). looks like your terminal can’t access [api.atlassian.com](http://api.atlassian.com). could you please check if your browser has any special proxy settings that allow reaching to the outer internet? also, could you please run something like curl -v https://api.atlassian.com/graphql?", "name": "", "is_accepted": true } ]

[ { "text": "just fyi this is still very alpha and highly likely to change without notice!\n\nglad that you’re digging it, but it needs some serious real designer love (and not just me hacking at it!).\n\nbut hoping that we can keep making moves towards making things look better here. always open to input and though…", "name": "", "is_accepted": true } ]

[ { "text": "hi piotr,\n\nsorry to hear you’re running into trouble.\n\ni just gave this a go on windows 10 and it was ok, but - i didn’t actually have time to go through all the steps in the tutorial.\n\nwhat i would recommend, based on your errors is that you try an atlas-clean in the plugin directory you created. …", "name": "", "is_accepted": true } ]

[ { "text": "as a workaround i was able to extract the contentpropertyindexschemamoduledescriptor via the pluginaccessor.\n\nfrom its pluginmodule the relevant contentpropertyschemafield can be extracted whose fieldname can be used to construct a com.atlassian.confluence.search.v2.query.termquery which can be used…", "name": "", "is_accepted": true } ]

[ { "text": "resolved this privately", "name": "", "is_accepted": true } ]

[ { "text": "hi [@kamil](/u/kamil),\n\nthanks for your question. yes, the feedback channel is designed to allow the cloud side of migration to communicate to server side to provide updates during the migration process. because of rules around gdpr and data usage, after a transfer is settled we remove everything related to tha…", "name": "", "is_accepted": true } ]

[ { "text": "yup,1.6.1 has description. <https://aui-cdn.atlassian.com/atlaskit/stories/@atlaskit/single-select/1.6.1/?selectedkind=%40atlaskit%2fsingle-select&selectedstory=select%20with%20descriptions&full=0&down=1&left=1&panelright=0&downpanel=kadirahq%2fstorybook-addon-actions%2factions-panel>\n\nloading states…", "name": "", "is_accepted": true } ]

[ { "text": "important: please use this solution for jira 8+ only. some problems have been discovered with the usage of this approach in jira 7.x. thanks to lukasz wlodarczyk for clarification. please take a look at his [reply](https://community.developer.atlassian.com/t/migrating-apps-to-jira-8-be-careful-when-using-jql-from-background-threads/25686/6) for details.", "name": "", "is_accepted": true } ]

[ { "text": "the problem is resolved using:\n\njira.trigger(jira.events.refresh\\_issue\\_page, [jira.issue.getissueid()]);", "name": "", "is_accepted": true } ]

[ { "text": "hey [@cris1](/u/cris1) i tested the translator app and also ran into some issues. not exactly the issue you describe but i was seeing 4xx responses while calling the translator api.\n\n[with these changes](https://bitbucket.org/atlassian/forge-issue-translation/pull-requests/5), i was able to get the translator app working as expected. these have been merged to master so could you try a…", "name": "", "is_accepted": true } ]

[ { "text": "hi mel,\n\nthanks for your reply. i created the suggestion, here is ticket: <https://jira.atlassian.com/browse/jracloud-74900>\n\ncheers,\n\nkamil.", "name": "", "is_accepted": true } ]