Aaron Williams Rising Star

Thanks for the lovely comment

I think this is outdated now. The don't notify myself option is only valid for email notifications.

Notification schemes do not have granular detail to allow such things as "do not notify yourself" This is only relevant to the notification bell, not email notifications. For example why do I need to be notified that I left a comment, completely unnecessary.

Ah so my issue is slightly different. I don't receive emails notifications I do everything through Jira. I know you can turn off email notifications for your own changes, but this option doesn't seem to exist for the notification Bell. 🫪

Hey @RZ I don't think this is possible, because how would you know who the customer is? Jira needs an account to be able to set a reporter. If you don't want users to create their own accounts but have ones created for them, you are limiting yourself to email requests. Thanks. Aaron. 

Hey @Thomas Ljungstrøm Have you checked the access portion of the project settings? And further to that check your user directory. It may be the case you allow customers to self sign up. Thanks, Aaron 

Hi @Susan Merola Instead of extracting the email to a custom field, why don't you have your automation set that field to a value if the alias address is used, and then use that in the queue. When issue created > IF alias email used > set custom field to "program name" Then in your queue use the custom field. JQL:…

Hey @Vicky Pagnaer A quick way to check for it is to hit "." on your keyboard and type "site", site optimizer should pop up. If it doesn't then there is a change it may need to be enabled in some way. Thanks Aaron 

@Ardalan Sepehri Does your workflow create a resolution status when issues are moved to done? Resolution status is the true "done" and will mark the issues as truly complete. You can check if it's set in the workflow, it's done via post function. Thanks Aaron 

Hi @Tamar Peer Not that this is the answer, but if it's only for some users I would start with a permissions check. Compare then to someone who is able to do what is needed and see if anything is different. Thanks Aaron. 

Hey @Brandy Richbourg Hope you are well. When you set up a service management project in Jira, one of the many settings is Email, with this you'll have the ability to set that as the email for the service desk. When users email that address it'll raise a ticket into the service desk you have created. There are setup…

Does your company use managed accounts? As you can creat a catch all organisation that adds users based on their email domain, but it'll only work if they all use one domain. The issue you currently have is that assigning the service-desk-customers to the issue level security is essentially wiping out the org. 

I think I may be missing the point of all this then. Are you trying to ensure all customers (Org or otherwise) can see all tickets raised to the desk?

Hi @Vishwadeep Sharma An approved domain is just you saying "anyone with this domain can have product access" not that they are automatically given it just by existing. It works this way for creating an Atlassian account, just because the have an email address that matches your domain doesn't mean they automatically have…

Hi @Mahnoor Arshad This will be down to the fact that the issuetypes you are creating aren't sub-task issuetypes, but standard issuetypes. Only a sub-task issuetype can be a child item of a standard issuetype. Task in this instance is a standard issue type, so it can have subtasks, but the Task issuetype cannot be a…

Hey @Todd Dobmeyer My first thought is that this would most likely be a permissions issue in the new instance. Being an admin doesn't necessarily mean the permission schemes are set up the same. I would suggest speaking with the admins around you with your concerns as they will be best placed to help make necessary changes…

@Francesco Lucci is this to restrict what Request types customers can see? This is the only use I can think of for setting security levels for customers. As typically customers can only see their own issues or ones the have been added as a request participant. The advantage of Orgs is that sharing is easier as standard.…

I thought issue level security was for back end use? I.e setting which team members could see specific issues based on a security group of some kind. A customer wouldn't come into that. If you prefer the ease of "People & Access" I would suggest adding all the customers from the Org, into that section and removing the Org.…

Hey @Francesco Lucci If the users are in an organisation that is linked to the service desk, they will already be customers. They do not need to be added to the "People & Access" section too. Thanks Aaron. 

Hey @BmOrchard Do you have a screenshot of the "structure" so I can see what it is you mean? This may help troubleshoot the issue. Thanks Aaron. 

Hey @Rebecca Maaser You can view archived issues in live projects via the archive issues tab (in software projects that is) You can only view archived issues in archived projects with the direct link to the issues themselves. As far as ok aware there isn't another way to do this. The easiest option might be to reactivate…

Thanks for getting back to me. I can see what it is you want to do, and it is a shame you can't natively show templates on a form field. My suggestion was going to be splitting these into individual custom fields on the form and bringing them all back into the single description field via smart values. But as you said you…

Hi @Toby Dennison Have you got an example of the ticket description template? Thanks. Aaron. 

Hey @James Traxler I have noticed this happing recently too, hopefully this gets corrected.

@Anzar I know this isn't quite an app but if you add to your phone's home screen it does actually install Atlassian community and it becomes "app like" Obviously there are no additional features but it does remove the web browser feel. Thanks Aaron. 

Hey @Alagu Murugan Krishnan Do you want this same action to be performed if one of the team created and issue via the create button too? Thanks Aaron. 

You will need to use Scriptrunner for this, as it allows you to build complex scripts that act as workflow blockers Do you have access to scriptrunner? 

And what if there are no linked issues? You won't get the instant feedback that you won't either way, there will always be a delay whilst the automation does it's thing. The only real option for immediate feedback would be a 3rd part app, like Scriptrunner couple with a workflow rule. Thanks Aaron 

Hey @thumuluru.shreya I have something working, but I need a more information to make sure I've got it right. Trigger: when issue transitioned to closed Issue fields condition: issuetype= bug AND Linked issue are present - link type: "causes" - condition: all match specified JQL: issuetype != "your desired issuetype" THEN…

@Anna Luszcak could you tell me the exact project type your roadmap project is?