Gal Fatal Community Champion

1. Yes! counting my 10 team events since 2018 2. Rovo Rovo Rovo

@Tomislav Tobijas thanks, yes if you can list the steps here it will help me (and maybe others too). Thank you Gal

@Brant Schroeder thanks But when I add the field it sets it as a HIDDEN and I cannot change that, so it's hidden from the portal :( any suggestion how to remove the hidden ?

That was more than 3 years ago. Everything is changing so fast, it was clear that Atlassian will stop supporting DC one day..

Thank you @Trudy P Claspill I created ticket to Adaptavist.

Exciting news! @Marie Casabonne Thank you for the excellent explanation. I'll share feedback soon.

having the same issue exactly. cannot setup 2 steps verification. Hope someone have solutions for it

I tried to use team in Jira. but...with no JQL support it's useless for many customers. The critical missing JQL is "memberOf". (same as in group)

Welcome Cindy! Paris is beautiful :) Regards from Tel-Aviv

Welcome and good luck Cidoni! hope to see you at the team events!

thanks @Jack Brickey that's what I also think. What I need is once someone share his manager then add his manager as a request participant in the ticket so he will have access it Any idea for this ?

@Lean Li I had the same need and found a solution. See the link below, how to see the summary of a parent in structure column https://tempo-io.atlassian.net/servicedesk/customer/portal/6/article/4128899180

Hi @Marc -Devoteam- Thank you, I did not think about the team-managed option. Now the challenge is to find in which team-manage project this field created as I have many of them. My opinion is Atlassian should block the option to create field with same name of system LOCKED field even if it's in team-managed project. or at…

Great news

@Aaron Rowsell Hi I believe it's full time employee of the company, but I give you my colleague email - you can send her email and she can give all the details. ayelet.ben-tzur@evokeplc.com Good luck Gal 

@vikram Hi Unfortunately no, they are looking for full time job position.

Thanks @John Funk , I was not aware to this app. Interesting.

@Marc -Devoteam- thanks. I work on it with Atlassian support.

Very helpful, thanks!

@Marc -Devoteam- thanks I voted for the feature request. o me it should be obvious to have import, if you have the option to export..

Thank you @Mark C . I voted and watch this issue.

Thanks, had the same issue (in cloud) and this solved the problem

Good news.

Hi @Alex Hall I think you can find answeres to some of your questions in this article I wrote : Navigating the Atlassian Cloud Sandbox . Take a special look at the "Copy data limitations". If you need to compare you sandbox environment to your production site, I recommend you to use tools such as Salto so you can be sure…

Hi @Bill Sheboy @Jack Brickey The idea of the Webhook is to let the user create bug from a user story. The automation rule update some fields with defaults. copy some fields from the user story and create a link between the new bug and the user story. So it's a quick way for the user to create a bug related to specific…

Hi @Jack Brickey sounds like a perfect solution. but when I try I geth error "the selected trigger requires the actor to be set to a user" :( :(

Hi @Jack Brickey thanks for your assistance. {{issue.reporter}} gives me the reporter of the existing issue, not the new one. Since the creation is executing by "Automation for Jira" which is always the actor in my case, the reporter becomes "Automation for Jira". Here is the use case: 1. User A creates a user story. He is…

Hi @Martin Benavides I need same, but for cloud. Can it work ?

Thank you @Hana Kučerová for catching this and letting me know. That was my mistake, I fixed it.

Thanks @Sebastian Krzewiński This is Atlassian "URL field" custom field type. I'll contact Atlassian support. Thanks