Rebekka Heilmann (viadee) Community Champion

For us, the lack of external collaboration is the biggest downside and the main reason we've not switched completely from Miro. We often work with customers and they need to be able to edit on these whiteboards and not just view (which is a newly available feature). Also, a lot of our Agile colleagues are missing Moderator…

Love that new badge!

Have you started fresh in Cloud or migrated from Server/Data Center? Have you imported projects or issues at some point?

I have plenty of use cases but still need to wait for some triggers and actions, especially around databases. Once they're there, it'll be super helpful!!

I love any summarization feature and hoping for the translation feature to improve in the near future.

I do love a good Frozen Yoghurt, complete with chocolate sauce, some cookies and strawberries (if they are in season)!

Hi @Siobhan Tiulentino and welcome to the Community, you probably checked whether there are required fields configured via the Field Configuration in that project? It might be, that not all required fields (per Jira config) are shown on the form so issue creation will throw errors. However it wouldn't explain different…

Hi @sandeep.singh and welcome to the Community, what Template are you using for the Export? It might be that someone created a Template (space or site wide) that for whatever reason restricts the export to the first page. With the standard Export that shouldn't happen.

Deutsche Original Version Guten Tag, Hello und Namaste. Ich bin eure Reisebegleitung für die nächsten Wochen, Monate… oder sogar Jahre?... und heiße euch herzlich Willkommen an Board von Atlassian Airlines. Schön, dass ihr euch für die Jira-Jungle-Journey entschieden habt. (ganz freiwillig natürlich) Die genaue Reiseroute…

Ah sorry - I've not double checked that before posting. I know for a fact that they can change the Issue Layout, but not tested anything else as we deprived them of their EPA rights before migration anyway ;) 

Hi @kate reeder Permissions for Automations are tied to Project Admin Permissions. A project Admin can only create Automations that are in the scope of that specific project. They cannot create global rules. Regarding Workflows and such: Project Admins can only edit Workflows, Screens etc. if they don't share their Configs…

Don't really have a clue, but can you double check if * your colleague is an Agent in at least one JSM project with active Incident Management & Alerts (active under Features) * has the "Alerts" Tab under "Your work" in the Nav bar? * if you are a "responder" to/owner of any Service (Feature "Service") in JSM or in Compass

You can switch off the Email channel. I'd think that would prevent issues being created and also comments being added. 

Thank you! I'll try that out asap - had some production issues this week so been busy, but will put it on my list and let you know.

Yes!!! One of my facepalm-moments of this week ^^

Hi @Wioletta and welcome to the Community, You can restrict the "Assignable" User permission to a "group custom field value". That way, the issue can only be assigned to the users from the current Assignment Group. You'll need to edit the Project permissions for that. However, I don't think that will limit the auto…

Hi @Dr_Win_ST you need to check the Project's permissions. Go to project settings > permissions. The permission you're looking for is "Delete issue". It's likely, that currently it is set to project role "Administrators". You would have to add "Users". Note: it's likely you are working with shared permission schemes. Any…

The "Incoming Mail" settings only apply to Jira (Software) projects. JSM projects have their own Email handler and all settings are under the JSM specific settings (Global/project). Hence you can ignore the missing handler. I know - you wouldn't be able to tell by looking at the Administration pages...

Nevermind. The execution user didn't have Log Work permissions.

Hi @Lisa Hanson and welcome to the Community, to "remove" a two column layout you simply have to copy the content onto the page where there's no layout set. You can just go to the bottom of the page and click outside the layout and add a new line. There is no way of switching the set layout back to "full width"…

Hi @Inna S the only solution I can think of will involve API calls and some scripting. * Get all issues of the version you want to inspect, Also get the version including all details * Get the change log (issue history) of each history and check for the entry where the issue has been added to the version - check the date…

Hi @Alain Kovacs I didn't know you could check that in the Administration, like @Rilwan Ahmed suggested. Works perfectly for agent level!! If you have lots of projects and Agents, and want a quick overview of how many Agents per project you have, creating project-specific groups works quite well. One of my customers has…

Hi @Tim Bonney you can only disable Email communication and therefore issue creation through email in its entirety. OR you could change one setting so answers to requests will be processed as comment. Go to Jira settings > Products > Jira Service Management > Configuration > Email "Yes, allow all emails that contain a…

Hi @Anagha Prasad and welcome to the Community, do you also see a "Quick Guide" on the right hand side or does it pop up occassionally?

Hi @David Hauer and welcome to the Community, can you access admin.atlassian.com and see whether your subscription is still active? The TLS Email has nothing to do with site availability.

Hi @Saurabh Chaurasia and welcome to the Community, "Updated" is not a field that holds its own value, but will essentially show the timestamp of the last action on the issue that will be reflected in the issue's history. With the Changelog/Fieldchange you can only access the current change (depending on the Automation…

Hi @Magdalena Lemur and welcome to the Community! Uuh. Interesting question, that I don't have an answer for straight away. I know that changing the project key will create an entry in a mapping table in in the database (or at least that was the case for Server/DC) so old key references will always be able to be mapped to…

Details are finally out now as well :)

Hi @Gerri Mills to my understanding this should only appear for Admins until published for the first time. I guess it's another "In App advert" then. Support might be able to deactivate but that always depends on the feature in question unfortunately.

Hi @Scott Beeson you initially only asked about the Hub. The Hub tab is only visible to Confluence Admins until you first publish the page. To hide it again, you'll need to * go into the Hub * Click "Edit" * Click "..." * Click "hide the hub" This will hide it for all "normal" users in case you already published it.