Susanna Babayan Community Champion

well it's not really possible imo issue history is not related to any permission/access directly, so you cannot limit it. nor you can edit it. for hiding the transition, you can check this post Hide transition in View workflow but it's up to test since I personnally haven't encountered this type of configuration. but…

@mekhak.bezhanian If I understood you correctly, you want to hide the issue transition history, right? as per my knowledge, it's not possible to hide data in the history section. you can't even delete it manually, it's stored in Jira

Hi @mekhak.bezhanian Is this happening on all of your issues or just one? Do you know if the issues were imported?

Hi @Martin Gibbons It does indeed seem like a strange bug. Does the same thing happen on other projects or it's just this one?

Hi @Hana Kučerová As per my experience, we use team-managed when there is a team in the company that would like to customize their project to the fullest and they don't have enough access to do that for company-managed projects (since you need to edit the schemes). Plus, it's a good start for someone who has never used…

Hi @Melker Valve Have you checked if the permissions in both of those projects are the same? Do the users have the same roles in both of those projects? Are both projects of the same product (both JSM or both JSW)?

Hi! Maybe it's a basic question but to be sure: have you checked if they're agents?

Hi Talya! Currently there seems to be no direct option to allow customers to edith fields in the portal (JSDCLOUD-93). Atlassian suggest forms as a workaround: How to allow customers to edit the Jira fields of their portal request using Forms

Hi @Nathael Dreymann I'm not sure there is a way to Bulk Change request participants (see JSDCLOUD-1269). You can check this article How to add/update/remove Request Participants using Automation for Jira maybe it would help you out.

Marco, I'll let others confirm, but as far as I know you cannot specify the card size (just the layout). since you added the Description field, Jira shows the whole description. maybe you'll need to remove it

Hi Marco! I guess the Description field was added to be shown in your board. And in some cases the whole description shows up since it fits the card size. Can you check if in Configure Board > Card Layout the Description field is added?

Hi! You can refer to these two posts with the same/similar questions: Find all issues created outside of normal working hours How to filter tickets specifically by time of day

Hi everyone! I've been with Atlassian for almost 2 years. I worked with JSM, JSW, Work Management, Product Discovery and Confluence. I had quite the waste experience since I'm a Jira Support Agent and I also use Jira as a part of my daily work. Sooo, hope to learn here as well as share my knowledge as much as I can :) 

Well, if the first option is for a specific instance, I'd rather have everything available for one product on one instance and then the rest on another one...if it makes sense 

Hi Anjali! I can only add to what @John C has already said: from Jira Service Management point of view, Request Types is what your customers see in the portal and Issue Types is what Agents see when working on issues. 

Hi! 1) for the first point you can add users into groups and then change their permissions in each space: for some spaces they can view it and for some others they cannot. 2) I'm not sure I understood what you mean here. "if we allow them to download files in that space, does that mean the space is shareable to everyone…

Hi John! I'm not sure but I think Anjali means how many issue types can be used for the same request type. As in, multiple request types can all be of the same issue type

Hi Koutarou! do you mean to send an email when the status gets changed to "THROTTLED"?

Hi! do you already know what you're going to use it for or no idea?

Hello ! tu veux dire quoi par "les dates des checklist" ? peux-tu stp partager une capture d'écran ?

yeah that's that. as far as I remember, Contributors cannot create ideas, they're there to kind of view them and "contribute" in that sense. if you want to create ideas in JPD, you need to be a Creator

Hi Sarah! out of curiosity: do you mean put them as reporter or as assignee? why do you want to assign them issues? 

my guess would be lack of permissions tbh...seems like you can only browse the project

Hi Irini! Might be a dumb question but are you sure that user has issues assigned to them and are you sure it's in the project for which you made the query?

Hi Anette! I don't have much info either but I did manage to find something on Atlassian Cloud Changes. I think since it's rolling out, there isn't much info and later on Atlassian will share more details as it's quite an important change

Hi Beyer! so just to clarify: you wish to have your developers access certain issues and you want it to be defined in a custom field, right? as per my humble knowledge, there isn't a direct way to give access to one issue for specific users, the contrary exists tho (with issue security schemes). what might be doable is to…

Hi! can you see the button on the top bar? Have you checked on Project Settings > Access? maybe there was something changed for Admins...

Hi everyone! My headware habit, if it counts, is always putting my hoodie on when being concentrated on something...I guess I need to hide my peripheral vision to concentrate only on what's in front of me :D

re ok so I got my answer: basically nothing happens, the email does still exist which means people contacting the email will not get an error message saying "this email does not exist", however, no issue is created and the emails are sent to "nowhere"

Hello, one question about disabling email ticket creation: what would happen to the customer emails that they're sending to the project address to have tickets created (after disabling the email ticket creation)? Are they going to receive a message saying the address does not exist or nothing's gonna happen?