Liam Green Expert

Hi @Michael Kobert I'm not fully understanding the question. Could you give an example of what you mean please? Regards, Liam

Hi @candy.pearson Unfortunately, there is currently no way of restricting the access, other than by user. I'd suggest submitting a feature request to Atlassian - but check there isn't currently one that matches your requirements. I've done a search but couldn't find anything. Regards, Liam

Hi @Ibrahim Alnuman Welcome to the Community. Have you checked the log to see why the email has been rejected? If so, what does this say? Regards, Liam

Hi @Sofia Grunspan If you go into project settings > email requests, then click the ellipsis you should see Manage allowlist in the options. If you add the domain of your auto-ticket here then it might help. You can also view the email log here to see why the email was rejected. Hope that helps, Regards, Liam

Hi @Smiley, Latonya Your SLAs should be project specific, and not across the whole instance. To hide the field, simply remove your SLAs from the related project.

Hi @Abracadabra Can you provide a screenshot of your notification settings please? Regards, Liam

Hi @Helen Pippard Not had this issue before myself. Can you provide a screenshot of what you're looking at and I'll see if I can assist. Regards, Liam

Hi @Jonathan Gonzalez I believe this should be possible, yes. Do you want this for all issues going forward, or just for the ones that are currently created? Regards, Liam

Hi @Patrik Bajer Welcome to the Community. Have you thought about using Automation to achieve this? If you're not familiar with it - let me know and I'll point you in the right direction. Regards, Liam

Hi @Hanno-Wybren Mook Unfortunately that would not be possible - each request is only linked to one issue type. I believe this is because of the potential for different workflows, which would not easily adapt if the issue type could be changed easily.

Hi @Nick Turner Unfortunately this isn't currently possible. There is an open feature request that you can vote for and watch: https://jira.atlassian.com/browse/JSDCLOUD-4276 Regards, Liam

Yes, John! It will see the reporter as two different people. Also, the @newcastle.ac.uk account would not have access to the @ncl ticket. The solution to that is to always add the other account as a request participant. Very messy from a notification point of view though. Regards, Liam

Hi @Nick Turner I don't think it is something you could put on a 'customer' request form, as customers would not usually have the ability to browse issues, so couldn't link them. A workaround would be to have the developer use the 'create' button to create the issue. Hope that helps, Regards, Liam

Hi @Kylie Baker Welcome to the Community! Does the name show as the original name on the agent view? To change the field name you need to click the cog on the top right, then issues > custom fields. You can then search for the field and rename it to match the customer view. Hope that helps, Regards, Liam

That's very strange - usually it would just have the Key not a link I think. Can the user confirm what they did to reply - did they include another email address? Email isn't an exact science for Jira, so even when it looks like you've done everything right it can still throw up an anomaly.

Hi @Tully Team Welcome to the Community! I'm not sure I can fully answer all three questions - but I will do my best: 1. Outgoing emails are called notifications in Jira. These can be customised in many ways - and you can learn more about this…

Brill, glad you found it!

Hi @Jeffery Stone Welcome to the Community! Your SLA should only count on days (and times) that are 'work days' according to your SLA Calendar - so if an issue is moved to the status on a Saturday, but you only work Mon 9am - Fri 5pm, then the SLA won't start counting until Monday morning at 9am. If your SLA isn't working…

Hi @Vugar Jafarov What happens when you start typing the name of a user that you want to add?

Hi @John Dawson Can you clarify what the subject was? Did it have the URL in it?

Hi @Ali Iqbal Welcome to the Community. Are you still experiencing this issue? What is it that you're trying to import?

Hi @SMT - Mustafa Demir If you set the requester as the customer that you would like then they will receive all the public updates on a ticket. Hope that helps Regards, Liam

Hi Rory Are you talking about on the portal or agent view? Could you provide a screenshot and we can see what you're looking at.

Hi @Alexander T. It sounds like Jira Service Management would fit what you need. Check out their product page: https://www.atlassian.com/software/jira/service-management You can find out everything you need, and start a trial from there. If you have any questions the just drop them in the Community and we will try to help.…

Welcome to the Community @Prashant Sangappa Shivashimpi 

Hi @Amy Ouzoonian Welcome to the Community! Great to have you here!

Hi @Divya Choudhary Welcome to the Community! If you've already checked with your admin to see if they're aware of the problem and not found an answer, for a specific account issue such as this you would be best contacting Atlassian support directly: https://support.atlassian.com/contact/#/ Hope that helps, Regards, Liam

Hi @ebenothmen I don't think this is possible with notifications out of the box, no. The only variables are key, summary and portal name. You could achieve the above with Automation - which you could also copy to each project. As you're on server, Automation is a marketplace add on. There is a lite version that is free -…

If you go to you Atlassian page, then click on either your avatar or initials near the top right - you should be able to go to your profile page. That will givee you your ID in the url at the top

That looks beautiful