Matthias Gaiser _K15t_ Community Champion

Congrats to everyone! And a special shoutout to @Joerg Mueller-Kindt and his very active ACE group in Berlin! 🎉

Hi Manish, I see several ways how you can automate these processes: * Jira Automation You can configure an automation rule to copy your comments to linked issues. So when you have your Software and service desk issue linked, you can setup an automation like this * Issue sync apps There are various issue sync apps which…

Hi @Adam George so what I understood is that you have in the Jira project A one issue for every project (not talking about Jira projects here) which contains the corresponding details for this non-Jira project. In Jira Project B, you want to create issues and select the values from the various issues in project A. I think…

Hi @cgoodin welcome to the community. Based on your description, I'm assuming you're talking about Jira in an on-premise installation. If you refer to customer support ticket - are you talking about Jira Service Desk (now called Jira Service Monitoring)? For Jira Service Monitoring/Desk, this could be a suitable solution:…

Hi @Ross Wicks, welcome to the community. Unfortunately, I don't think this is possible at the moment. You can vote for the feature request here: https://jira.atlassian.com/browse/JSDCLOUD-4222 Cheers, Matthias.

Hi @Vielbert Victorio it would be great if you can elaborate a bit more what escalate you mean? You've categorized this question into Jira Software - and I'm not aware of an escalation there. How about adding a screenshot of what you're seeing? Cheers, Matthias.

Hi @Grant Kidd thank you for your post. I feel your pain - and I also think sometimes the authentication takes way too long which it shouldn't. I think there are two thoughts to mention: * You can browse the Atlassian Community also anonymously. You can prove that by trying to open this post in a new "incognito window" and…

Hi @Aleksis Kermorgant, welcome to the community. Your problem is a common one in writing documentation. I'd recommend the Include Page Macro to you. This macro enables you to embed a complete page into another page. In order to solve your problem, I'd suggest to * Split your page A into 5 pages (A1 - A5) * Add two include…

I can back what @Gary Fitzgerald said. I'm working for the team behind Backbone Issue Sync (similar to Exalate) and we see many customers using our product in such a scenario. I'd say the benefits are: * You can have different license tiers for the internal and external Jira. * You can choose which fields you want to…

Thanks again @Fabian A_ Lopez _Community Leader - Argentina_ Florida_ California_! Here's also the direct link to our rock the docs page where we try to give tips and advice for technical documentation inside Confluence. And I'm sure @Matt Reiner _K15t_ is happy to talk to you.

@Kristján Geir Mathiesen I get a 404 error when opening your link. Is it the correct one?

Hi @Simon Rigler thank you for posting your question. I'm one of Backbone's product managers and I'm happy to jump on it. I guess I have some good and bad news for you. The good news It is possible. The bad news The process is a bit cumbersome for your use case - but you may judge yourself. How you can do it You can tell…

@Fabian A_ Lopez _Community Leader - Argentina_ Florida_ California_ , thank you for mentioning me. Since @Piotr Piasecki is looking for Cloud solutions, I've added a new answer to not confuse him - or anyone else reading the thread.

Hi @Piotr Piasecki, as @Fabian A_ Lopez _Community Leader - Argentina_ Florida_ California_ mentioned that sounds like a perfect use case for some of our apps. It's on the heart of our vision that you can communicate your product value to your customers. Since you've stated that you're on Confluence Cloud, I can see the…

Hi @Richard Mathews welcome to the Atlassian community. I'd like to ask you to explain in a bit more detail what you want to achieve. I can see some different directions here: * Application linking You can create application links between your Jira instances so that you can use issue links to link related issues together.…

Hi @desarrollo, did I understand it right that you are looking for a way to synchronize some of the tickets from your Jira instance A to Jira B and want to be able to control what data (fields, attachments, comments) you actually exchange? If so, that's the use case where issue sync apps usually come into play. These apps…

Hi @GG , I'd recommend getting in touch with the Exalate support via support@exalate.com. They should be able to help you. Cheers, Matthias.

And awesome poem, @Darline Auguste! That's so fun to read!

Congrats @Thomas Schlegel. I can just back whatever was said here. And I'm really looking forward to some boardgames with you some time on some Atlassian Event. I didn't know about @Monique vdB's boardgame passion so far - I actually thought about hosting some boardgame event at a past summit, but somehow didn't find the…

Hi @Ricardo Augusto Pereira de Matos, to add on what the two other leaders said above: You need some tool to automate this synchronization. What you describe is a classic use case for an issue sync app. An issue sync app lets you define rules/scripts in order to keep issues across two projects (even across Jira instances)…

I felt deeply honoured when I was asked to join the CAB - and I'm happy to be part of this group so that I can give something back to the community which I used for tons of advice in the last years. While I'm usually more active in the online community, I really look forward to actually meet some people again in Atlassian…

Hi @Sigrid Schoepel, I can think of two ways how you can get to a solution: * Ask the Atlassian Support Since no one here seems to know if Automation can/should do that, you could ask the Atlassian Support team for that. And if it doesn't work yet, ask them to open a feature request, so it might work some time in the…

Hi @Debankur Ghosh, there are various options how you can collaborate in such a scenario. As @Dirk Ronsmans pointed out, it would be great to get some more insights into your scenario. In general, I can think of these options: * (Shared) user account in the other instance You can directly give the other people access to…

Hi @Frank Winkler I'm Matthias from the Backbone team. I have to admit that I didn't work too much with Scriptrunner's behaviour functionality, but your script fields solution sounds good to me. My understanding of the solution would be: * Create a scripted field in the source instance & don't show it on a screen. * Define…

Hi @Pierre Kande in order to move the issue data from one instance to another, you could also use an issue sync app from the Atlassian Marketplace. These apps let you define rules how you want to sync your issues with some other Jira instance. You can then decide if you only want to do a migration (one-time sync) or if you…

These are great news! Thanks a lot, @Alison Huselid!

I tried it basically with the same request - and it worked. Does the error tell you more what is wrong? Maybe an invalid accountId? Here's my request: { "fields": { "summary": "create test", "project": { "key": "CA" }, "reporter": { "accountId": "The_accountId_of_the_user" }, "issuetype": { "name": "Task" } } } 

You can do another rest call before which resolves the accountId via the email address. I'd recommend using the "find users by query" REST API for it. As query parameter, you can specify your email address. From the response, you should be able to parse the accountID

Hi @Matias Costa Meneses, based on your information, you mentioned that you're using a Cloud instance. Atlassian has disabled user names on Cloud instances, therefore you're not able anymore to set a reporter via a name. You should use an accountId instead. The accountId is the unique identifier of your Atlassian account.…

Hi @Rana Asif Rubbani, I'm happy to give you a reply. I'm working for K15t, an Atlassian marketplace partner, and we do lots of apps with their (REST) APIs on Server, Data Center and on Cloud. It's totally fine to create your own custom applications which interact with Atlassian's APIs, there's no extra licensing agreement…