Comments
-
Thank you for sharing you solution.
-
@Garret Zhang, can you elaborate what you'd like to use the webhook for? I don't see the need for it. If you want to do it with automation, I'd suggest it similar to @Trudy P Claspill. Creation is as easy as: * Trigger: Version created * Then: Create version (in the other project) * And: Set entity property I'd use an…
-
I don't have a real solution, but an alternative. You could think about using a multi-select field instead of components. That would be easy to share across multiple projects and has a similar functionality.
-
Hey Yurii, I think, these parameters should be contained in a REST API call to <JIRA_URL>/rest/applinks/1.0/listApplicationlinks. Maybe that helps to move your forward? Matthias.
-
Hi @Yurii Zhatkin while searching for a solution to your problem, I've found this guide. It explains a solution for Jira Cloud, but I think this might be also possibly be used on server/Data Center. The central part of the solution is the /remotelink Jira REST API call - and this API is also available for Server. Maybe…
-
Hey Jagoda, welcome to Atlassian's community. Automation I tried to follow your setup and ran into the same problem. I got No Actions Performed as well. I think, I've figured out the reason for this. It seems there is a difference if you link on the screen of issue A-1 to A-2 vs. on the screen of issue A-2 to A-1. Issue…
-
@Bill Thang - there's no easy straightforward way to add fields to the create linked issues screen and here's the corresponding feature request to watch/vote for. But I was able to find this workaround description how you can still add fields to the linked issue screen. You need to mark them as required in the field…
-
Hi @Tmz welcome to the Atlassian Community! In order to synchronize issues between both instances, I'd recommend to use one of the issue sync apps from the Atlassian Marketplace. These are designed for exactly this scenario to exchange issues between different Jira instances. Please note that I'm part of the team behind…
-
Hi @ejanis I'm part of the team behind Backbone Issue Sync. I'm aware of the reviews you've talked about - and also of the circumstances of their situations. I can assure you that Backbone is running on customer instances reliably for around 10 years now. Feel free to try it out yourself for free - or book a demo with us.…
-
Maybe to add: If you're a partner, don't use these support channels, but rather use the Developer and Marketplace support portal.
-
Hi @Chris Shepherd I don't have a complete script, but an idea how you could possibly achieve that. You might know that Jira has activity streams which show all recent activity on a global level or per project. It's also possible to filter the stream by a username. You can do so via…
-
Hi @Marta Mita, as David pointed out, you can achieve such a behavior using Automation. And it's important to store some relation how the two issues are related. (Side note: The ui action clone already adds the issue link "clones", I wonder why Atlassian chose a different behavior for the automation rule). If you want to…
-
@Antonello Storelli I can confirm that @Ash Yadav's answer is a good solution to your challenge. You can also read in his linked thread various recommendations of tools fitting for this use case. I'd recommend to search for 'issue sync' apps in Atlassian's Marketplace. This will give you an overview of all the available…
-
Hey @Istvan Fay I gave a talk last year about cross-company collaboration scenarios in Jira last year. It mentions 5 ways how you can collaborate: * Use Email for the exchange & manual update in your Jiras * Allow the users of one company to access the other Jira and use permissions/issue security schemes/etc. * Use a…
-
Hi @Gerben Wierda first I'd like to advise you to use the Developer Community for such type of questions - you probably get better answers over there. Having said that, I believe the API call fails due to a mismatching scope 😏. In the API docs, the scope for this method is read:page:confluence. You defined…
-
Congrats on getting it resolved! In order to make it easy for others to know which solution helped, please also accept the answer via the green button on top of this answer. Thank you! 😀
-
Hi @[deleted] your question might get better answers in the Developer Community. I wouldn't mess around with writing own ClassLoaders or interfere with system classes. You don't know what else you'd need to handle so that you don't run into inconsistencies. I'd rather check if you can unit tests the parts where you do your…
-
@Ditte Simard, posting your topic here is for me the first sign that you're brave enough to take some action to not stay alone throughout the conference. Congrats to that 👏 When you've talked about an area for "People Seeking Conference Buddies", immediately the Atlassian Community booth came to my mind. At the community…
-
Hi @Anne Menninger your rule looks good to me. I was able to successfully copy components from an Epic with your rule. I have two guesses where the problem may be: * Did you create an issue of type Task or accidentally another one (as I did in my tests)? 😏 * What are the details of your last rule? Did you also define it so…
-
Hi @Magdalena I'd recommend that you check out issue security schemes. With an issue security scheme, you can decide on an issue level which group of users should be able to see it. For the issues which can be seen by every user of this project, you could just assign no security level for the issue. For all internal…
-
Ah, I missed that part - my bad. I believe for server, the other answer is correct that this isn't possible :/
-
Hi @Moemen Dhifallah welcome to the Atlassian Community. Your request looks basically fine. The only problem I could see might be the reporter and the accountId. Can you try to create an issue without specifying a reporter? If this works, you might want to check if the accountId is correct. Cheers, Matthias.
-
Hi @Dariusz PAWLAK every issue belongs to an issue type and this has three possible screens - for viewing, editing and creating an issue. These 3 screens are assigned based on the issue type and the project. In order to retrieve them via the REST API, you can call the following endpoints: * Get issue type screen schemes…
-
This is correct, @Dave Mathijs. It needs to be done this way, so that all the schemes can be deleted, otherwise you'd get some warning that the scheme is still in use by the trashed project. That's also one reason why the UI is only accessible from the admin section to not make this action too accessible for accidental…
-
Feedback Welcome Although this is a free non-supported app, we'd appreciate your feedback how the app works for you or helps you in your migrations or other tasks.
-
Special shoutouts go to: * @Sai Tharun Lakkoju (K15t) for the implementation * @Anshuman Dash _K15t_ for coordination of the project * @Umer Sohail _K15t_ for spreading the word.
-
That might be a dumb suggestion, but have you tried to scroll right in your first Jira 1 screenshot and then you'll see the column selection?
-
@Adrian Smith, I can also confirm what @Steffen Opel _Utoolity_ said. I work for a marketplace partner and can see multiple Data Center community licenses for our app in our license report. At the same time, I'm using a community license for my voluntary activities including apps. Hmm.. if I try to order via…
-
I'd be in @Dániel Ballabás - catworkx and would come to Berlin, but "unfortunately" I'm on parental leave and rather take care of my kids this time. Don't hesitate to suggest sth. again 😁
-
Hey @Nadezhda Hristova since you're looking for a solution without apps, I'd recommend Automation in order to keep your tickets in sync. It's a bit cumbersome to do so, but it's possible in general. You'd need to setup some automation rules like this in both instances: * Send the creation of an issue* When: Issue created *…