Daniel Ebers Expert

Hi @Ufuk Fakioglu from your screenshot it looks like the Jira "Core" mailhandler is used - in case you are indeed using a Jira Service Management project there is a different approach using "email channels". In case I interpreted the screenshots right and you are not yet using "email channels" it would be an idea to use…

Hi @Rose Sayegh if I understand you right the trigger is a public comments (which means nothing else like a 'reply to the customer' in general). This automation rule should get things done - could you please check if it works, to be honest, right now it is untested. Regards, Daniel

Hi @David Meredith when removing the field from edit screen but not from view screen - like Fazila stated previously - the requirement should be absolutely covered! The basic logic (using automation) is perfect, there is no out-of-the-box solution available - so just keep what you have, this is a very appropriate solution.…

Hi @Sneha Kumari I was under the assumption your ask is for "Server" as there was no indication you would be using Jira Cloud. The initial requestor tagged the question with "Server" so without further explanation we assumed you would be asking for Server, also. On Jira Cloud there is no behaviours with Script Runner, I am…

Thanks for clarification, that suggests the mail channel in this case is fine and only some sort of Automation comes to mind. You would need to check all potential occurrences for Automation (incl. Workflow Postfunctions) to see where the doubled requests originate from.

I see, yes, this will count as "Issue Updated" event. From my understanding you cannot suppress notifications in a way you want it to work. You could remove some recipients from Notification Scheme but this is probably not what is desired (it would affect many other updates to issues, too). To my understanding you…

Hi @tina.raftopoulos adding to the great information Linda already gave to help you I found a bug which documents this behaviour: * Adding a next-gen Project via Filters to the Classic Board shows the Epics of the next-gen as unlabelled Issuekey https://jira.atlassian.com/browse/JSWCLOUD-17761 At the time of writing these…

If I understand you correctly the issue persists? If so please check workflow post functions in the create transition and if there are any Automations which are in place to set a security level after a request is created. First check (the easiest one) could be a quick look if Issue Security is configured for the project.

I agree with Markus. If possible please have also a look into the second log. From the first log there are some connection issues visible. Those errors are worth having a deeper look, also - I guess. However, it might be a different issue not related to the doubles mails you encounter.

You probably could set a label upon reply from a customer and maybe remove it as soon as the Agent replies. Using Automation this should all be possible. As Queues rely on JQL you would need to filter for the label.

Hi @Heinrich Graupner in case the issues are linked (using Issue Links) or they have some other kind of relation (Issue -> Sub-Task for example) you surely could use Automation. Please also check: * Jira Automation - all the resources you need in one page…

Hi @KIRAN KAUR while I absolutely agree with Sagar including the provided links it could be worth thinking about the requirement in a way where an experienced partner could help. Atlassian partners are experienced in complex upgrade and migration scenarios. Especially as you stated you are currently on a rather old version…

I really like the idea. It shows that there is activity in updating the knowledge base, also the initiative itself shows Atlassian is caring for the content. For the content itself I am with @Dave LIAO - it would have to be that a specific updated content is of personal interest or offers something new to explore, which is…

Hi Clark, Jay & Diane, I am wondering if "project properties" could have a positive impact. Seeing Clark stated it is a server installation I opened the API reference to gather details. While not documented extensively I feel it could be at least a start for a discussion/evaluation:…

Hi @[deleted] there are some differences between both project types. For the moment it would suffice to understand which type of project you are using so Community members can better suggest a solution. You can learn about the differences here:…

Hi @Lauren Pennisi based on previous knowledge the property "jira.permission.work.denied" can only be set in the environment of workflows - not directly on an issue, but please correct me if you have seen this feature somewhere. In case it is only for use within a workflow it won't help you - this is more an on/off switch.…

Hi @Tony Vlcek outgoing email logs for Jira Service Management Cloud is something still to come (https://jira.atlassian.com/browse/JSDCLOUD-4698) - you could vote for the issue and watch it in order to keep updated. Also a "blind copy" that goes out to the customer cannot be dispatched to you - in terms of a tap or an…

Hi @salvarez for Jira Service Management there are two logs you can view - a processing log and a connectivity log. More about them you can learn here: https://support.atlassian.com/jira-service-management-cloud/docs/about-email-logs-in-jira-service-management/ Have you had the chance to look into the logs? If so, are…

Hi @Sneha Kumari sure thing! On https://scriptrunner.adaptavist.com/5.6.8/jira/behaviours-overview.html you will find documentation for Behaviours and especially documentation on making fields read only. You also can narrow this down to groups. This is what the documentation refers to in the beginning: Making a field…

The first paragraph refers to the global permissions that you can adjust if you are one of the Jira administrators (which we understood this would be the case). It is the part Alexander mentioned earlier: You can remove "Create next-gen projects" permission from users through the Global Permissions Management…

I agree with @Thorsten Letschert _Decadis AG_ that your requirement will not be met by that way of implementation. The "Disable Notifications" event as such is fine. You could involve it in any post function of any Workflow (transition) you wish to be "silent" (depending on your actual notification scheme but it *could* be…

Hi @shrikant maheshwari from reading your requirement using feature fast-track transition from Script Runner could be an alternative. I found a similar discussion which might be helpful: * Is it possible to close the parent issue when all linked issues are closed?…

Hi @Yulia Zhyliaieva no solution right now - but a question: if you rename one user (S... ...huta) will the other one be renamed as well? If so, that would be a serious finding - if not there must be (somewhere) a duplicated account for whatever reason. Is there any chance to try to rename and report back what you found…

The try to retrieve the project lead from the drop down field is having exactly the problem - the 'null' value for Project Lead. The workaround was therefore to hard code the values until this will (maybe?) fixed some day. I am not sure if there are any other workarounds - but let's see what other Automation experts might…

Yes, when there are only administrators available, and you have no further accounts, then they will be allowed to create projects (Users with the Administer Jira permission can always create next-gen projects, even if that group is removed from this permission.). When you click on Jira Software, for example, there will…

I see, it totally makes sense. I tested to access the custom field representing the project picker. While a JSON-response came back the project lead of this reponse is always 'null' - there are reports in Community that this is the case for the project lead in many cases. However, sometimes it just seems to work. There is…

These are not the server logfiles but something that was gathered from the console of your browser. I suggest double checking with your server administrator like said previously if any error from logfile is visible.

Hi @Theodoros Karipidis if I understand you correctly Automation is setting and removing labels, perhaps alongside with other desired actions that are required for your teams. At least setting and removing labels trigger, from what I know, an "Issue Updated" Event. This event then leads to have an email send - namely where…

Hi @Ivonne Borloz you have already received many good information from Sagar and Alexander. Please be advised that in Jira Cloud Free there are some limitations, also when it comes to Apps. Some Apps will have a reduced featureset as long as they operate on top of a Free plan - some will not work at all. Please in any case…

@Vero Rivas I discovered an update from 05/05/2021 here in group where it says: Harvest confusion. The recognition module gets very confused when someone breaks through the top level, causing various errors. At one point it looked like people were no longer accruing points. We've released a special commemorative badge you…