Alex Koxaras -Relational- Community Champion

Let's hope that she can resolve your issue

@Kortüm Thomas good to know that! Try it and let me know here if that worked out for you!

tI don't know if I loved them, but for sure I was following the trend back then. So without any sign of embarrassment I used to wear the following products (some images I took from previous posters): Funny pack. Super useful and handy to store....eerr... nothing of importance since at the end of 80's I was about 11 yo. Fly…

@Monique vdB hiiii! I've completed a long time ago the fri-yay mission, but I can't see the badge on my profile! How easy is for you to check it? <3 

Hi @Blair In which product(s) you granted access to that user?

Maybe then this will help https://confluence.atlassian.com/security/articles-951406100.html

Hi @Gergo Matyas In your case I would create in a project of mine (or in a company "general" project) some issues with the work you are doing most often, like the ones you are mentioning. And then I would simply log the time spent on each of this.

Hi @Rodolphe Galland and welcome to the community, Go to your backlog and * click on the ellipsis menu (upper right corner, three dots) * Go to card layout and find the field you want to add (in your case business value) * Go back to your board * The field value will be displayed below the issue summary

@Jan Milata there isn't one yet. I would suggest to watch this page https://www.atlassian.com/trust/security/advisories for any news concerning CVEs affecting Atlassian products

Hi @Bertalan The instruction you were reading are for server/DC. Can you please take a look at those for Cloud (https://support.atlassian.com/confluence-cloud/docs/subscribe-to-team-calendars-from-microsoft-outlook/) and see if you can get the job done?

Hi @Victoriano Fernández Tomás and welcome to the community! I'll mention Theodora Boudale to see if she will be able to assist you!

Ηι @Nicholas Ren The "Discovery" you are referring to, might as well be a column name and not a status. You have to go to board settings -> columns and see which status(es) correspond to that specific column. Most likely, there isn't such a status.

Glad to be of assistance @Malte Redmann . Kindly mark my answer as accepted, in order to help others in the community. Thank you!

Ηι @Jan Milata Please take a look at this https://community.atlassian.com/t5/Confluence-questions/Does-Confluence-server-7-13-7-use-Apache-Commons-Text-v-1-5-1-9/qaq-p/2167474 where a member of the Atlassian team replies. Currently Atlassian is investigating.

Kindly mark my answer as accepted in order to help others. Thank you!

@Thankamol Luanglarppaisal ohh! Yes, you are on a TMP (team managed project) and standard issue type have this wording. On CMP (company managed project) there is a differentiation on child & subtasks for Epic and Standard Issue Type correspondingly. 

@Malte Redmann What exactly are you looking to achieve? Groups created in Jira can also be found in Confluence. However group creation is made by a central point, admin.atlassian.net. To have access to this, you have to be a site admin, which according to what you posted here, you are.

@Kortüm Thomas The way I would approach this problem is by: * Creating X custom field with different supplier choices based on region * Use FORMS on my request types * Use conditional sections on the said Forms Forms have the ability to show/hide sections based on choices from "closed-answers" fields, like single and multi…

Hi @Naresh Do you have any apps installed on your DC instance?

Hi @Thankamol Luanglarppaisal and welcome to the community, Child issues show the epic <-> standard issue type relationship and you can't change its wording.

@Riko everything you need to know about guest in confluence can be found here: https://support.atlassian.com/confluence-cloud/docs/invite-guests-for-external-collaboration/ Keep in mind that "Guests" are currently in beta version.

@__ Jimi Wikman you can't add a parent to a bug. You could add a linked issue of a parent-child relation, but not an actual parent. To do that he has to create a bug subtask. And again story, out of the box, can't be a parent of a bug. Still a new subtask has to be created and named bug or similar.

@Natalia Trofimov morning! For your rule to work I would keep only the components to edit the old value. The rest, as I see it, are obsolete. Then edit the issue and use the advance editing field and enter the following JSON: { "fields": { "YOURFIELDNAME": { "value":…

Hi @Ajanthan Muraleetharan No you can't in the sense you want them to be. What you could do it to create a subtask called "Bug" or similar and then you will be able to have standard issue types as parents.

@Riko if by "restricted files" you mean "restricted pages" you have to see if that user can view these pages. If not, he will not receive any notifications. You have to also make sure, that this user has opted in for notifications via his profile page.

The above will be valid if that guest was at least one time user. If it is a guest from the first time, then probable the "suggest changes" will be greyed out, and I don't think that you can change anything. They have their own atlassian id and they should change it.

Hi @Kristen Cote Guest is currently on Beta version and may not include all possible functionalities. However, if you have invited that user as a guest, then from user management you can "suggest changes".

HI @Kortüm Thomas You can't do that. What field you place on your request types, these are the field that are going to be visible for all customers on that project. What are the values of these two fields? How are they different from each other?

Hi @Natalia Trofimov The best approach would be to: * Make the specific field read-only (meaning remove it from the edit issue screen) * On the workflow(s) of your issue type(s) create a self transition called e.g. "Change Field Value" * On that transition add a condition to be visible only for user who belong to your…

Good to know! Kindly mark my answer as accepted in order to help others with the same question :) Thank you!