Guilhem Dupuy Expert

Hello @Michael Presneill , It's normal that you don't have an extra dropdown, it doesn't appear this way. You could check from your "Project" menu, where Jira lists all the Jira products you have access to : A green category should appear if your Jira Service Management app was downloaded successfully. If you're still not…

Hi @Sara Santucci , You could check from the Project settings => Issue Layout, which is a quite recent functionality. Your field might be is the "Hidden" section which would explain why it doesn't appear on issues. Let me know if this helps, Guilhem

What you suggest is actually a pretty good idea, there's always a chance for human error but at least you get rid of the unnecessary notifications. To avoid human error you could store the name of the customer in another field, and create another automation rule that will put in back in case the issue needs further…

Another option would be to export the issues of your next-gen project in an Excel of CSV file, and then re-import it in the classic Jira project. This should allow you to make sure that your old fields are mapped to the correct new fields

Thanks mate, good luck to you too.

Hello @Prabhu Chilukuri , Normally if you go to the next step, you should have the opportunity to map these fields with your new custom fields in your classic project don't you ?

Hi @Joanna Bajda , You could add on option in your automation rule but it will be case sensitive; By adding the following compare value condition : {{issue.comments.last.body}} does not exactly correspond to regular expression "Thank you" Let me know if it helps, Guilhem

Hello @Laura Bennett , Maybe you could try having a look at Jira Automation Rules, that can automatically create an issue if you have the right trigger. Regarding your problem, you could for instance create an issue when you receive a Webhook that could be sent by the alert for instance. Let me know if it opens up a trail,…

Hi @Stephane Zoko , unfortunately this add-on only exists on Server and Data Center and I don't know any equivalent on Cloud

Okay good to hear @Erin Blomert , that was definitely an unexpected error and it's nice to hear that it was resolved so quickly ! Have a good day !

Hello @Rodriguez, Jhon Ronald , If you are using a jira service management project, the best way to do this is to create an SLA computing the time since when your issue is resolved, and to use its value in an automation rule. For your automation rule, I recommend the "Planned" trigger that you start once a day, which…

Hi @Gajanan Sasane , You could try the follwing JQL : created >= "2021-01-01" AND created <= "2021-03-31" Let me know if it helps, Guilhem

Hi @Gajanan Sasane , You could try the following JQL : resolution IS NOT empty AND "Name of your SLA" = everBreached() Let me know if it helps, Guilhem

Hello @Erin Blomert , I know that such an error can be returned when the name of the custom field is updated by an Admin; now if no Admin is regularly renaming custom field this shouldn't happen. Another possible explanation could be with your Atlassian licence payment; if you're late on your licence renewal it might first…

Hello @Stephane Zoko , As far as I know the functionalities you are looking for are not available directly on Jira, the only way to bypass this limitation would be to download an App from the Atlassian Marketplace. For instance regarding the displaying of a field depending on the value of another I already used the…

Hello @Sean Calfe , Unfortunately there is no better way I can think of; However if your users are delt with using managed accounts you could try to deactivate them all temporarily from your new Confluence and re-activate them after the migration. Once again I never tried this manoeuvre so you should definitely try it on a…

Unfortunately I don't know how you can get this information specifically if you don't have the Site Admin access; I guess you'll have to ask people until you find the right person.

Hello @Marta Michaliszyn , It's a brilliant idea to create groups in order to make easier the permissions administration on your side, but unfortunately, you need Site-Administration or Organisation Admin permission to create such a group. The only way for you to do this is to contact your site Admin and request the…

Hello @JLim , The good news is that what you are trying to do is a native functionality of Jira ! You can set this using the Field Configurations available from the Jira Settings => Issues menu. Then, according to your example, you would have to create 1 Field Configuration for the Tasks, where you would make the field…

Hello @Shanjidha Akhter , I have a few question in order to make your question clearer; firstly which product are you using ? I guess it's Jira ? And secondly, what is this LEVEL you are talking about ? Is it a custom field ? And if yes, of which type, and which values does it allow ? And to try and answer your question,…

@Robin Sundström My bad, I misread your question I thought you were asking about Jira, sorry. I'm not using Opsgenie hence I won't be able to help :/ I'm going to delete my answer once you've read this message in order not to mislead anyone else.

Hi @Sean Calfe , There is no way to disable completely e-mail notifications in Confluence Cloud but I see 2 options you could use / try : * Tell the users to unsubscribe to notifications from their settings. It would highly decrease the number of notifications they should recieve * When there are too many notifications at…

Hello @SimonaS , Unfortunately, when you are using the Free Plan of Confluence you can't edit the permissions and access to your site; any user who is logged to your Confluence instance can view, create & edit pages. As a result there is no way to create "internal" documents on the Free Plan, I'm afraid you would need to…

Hello @Robin Sundström , You could implement such a solution using Automation for Jira where you can define the time period using a CRON expression. Would that work for you ?

Hi @ADyPo , Yes indeed it doesn't seem to work, another way to do this would be to create an Automation rule that would copy the value of the "Reporter" field which is automatically gonna be set to the logged in user during the creation from the portal (if you didn't set it otherwise). You will then be able to copy this…

Hello @Wasiq Dabir , When you'll close your current Sprint Jira will give you 2 options : close the unresolved issues or put them in your new Sprint. If you put them in a new Sprint, they will be in the desired column when you start it ! Let me know if it helped, Guilhem

@Alexey , you can re-use the field configurations, workflow schemes, issue type schemes etc... that you created for your previous project, but you can't automatically copy the requests types and the information you manually put in there unfortunately. You won't have any better solution but copy them manually :/ The only…

Sorry @Alexey ahah, I completely agree with you, this feature would give a lot more flexibility to the administration of JSM projects but unfortunately it doesn't exist :/ As far as I know you don't have any other choice but to recreate them 1 by 1. To be honest, the task is quite repetitive but it is quite quick to…

Hi @Alexey , Wow, that is quite a messy situation you got into 😄 ! It happens a lot don't worry, there is a solution to this, I would suggest you to try the next few steps : * Create another set of Request Types for every request type which is problematic, but this time using an issue type that belongs to your project…

Hello @Amitava Mallick , I'll give you an example of the automation you're trying to set that I used in several projects : Let me know if it helped, Guilhem