Hana Kučerová Community Champion

Hi @DipakP , welcome to the Atlassian Community! How exactly did you delete the file from branch1? Did you commit this change back to branch1? I think you get this error message because there are some non-commited changes now.

Hi @Nagappan Murugappan , resolutions are in resolution table: select id, pname, description from resolution

Hi @kiranmai genkolla , it should be the same: {{issue.custom field name.summary}} See here, in section {{issue.InsightField}}

Hi @Viru Hosamath , I found out your question has been answered here.

Hi @Albert Manuel , which type has your custom field? Thank you!

Hi @Chris , welcome to the Atlassian Community! Let's dive into this :-) Usually in these cases there are some JSM projects operated mainly by support teams and some JSW projects operated by developers. When issue is created by customer to JSM project, JSM agent looks into it and if he finds out, some development needs to…

Hi @Humberto Gomes , probably "Request participants" could work here - these are the users, with whom is the issue shared.

@Kevin Yi Great. If you have any questions, don't hesitate to ask :-).

Hi @Nicole , I also wasn't able to find anything about possibility of integration of these two products. Maybe you can also ask CrazyEgg about their plans in the future?

Hi @Stephane Curinckx , yes, there are some applications, which enable you to do more like: * Customer Satisfaction Survey for Jira * Surveys for Jira | Jira Customer Surveys * Ovyka Satisfaction for Jira But to be honest I didn't try any of them, so I cannot do any recommendation here.

Hi @vfeddewar , it seems, there's something wrong with your CSV file. If you open the CSV file in the text editor like Notepad, how does it look like, especially the second line? Can you share it somehow? Maybe it will be enough to just paste here a few first lines. Did you try to contact the vendor of the…

Hi @Shawn Pennington , welcome! If you are having any questions, don't hesitate to ask, we are here to help :-).

Hi @Bravo , welcome to the Atlassian Community! If you are using this Power-up, unfortunately I don't think it is possible, there is no such configuration to set this.

Hi @Stephane Curinckx , I don't think it is possible. I believe the rating is not set by default, so it doesn't affect statistics.

Hi @THE STORY TELLER , sure you can search issues using JQL like: labels in ("xyz") AND status = "Closed" AND issuetype = "test" AND automation = "Complete" If you are happy with the result, you can save this JQL as filter and use this filter in pie chart gadget in parameter Project of Saved Filter.

Hi @THE STORY TELLER , in pie chart gadget configuration you need to set two parameters: * Project or Saved Filter: the list of issues you want to work with * Statistic type: the field, which will be used to group the issues It seems to me you mean you want to have more parameters for grouping, but this is not possible…

Hi @serge calderara , please try: fields.issuetype.name or using your variable issueType.name

Ok... Is this new set of watchers still the same or not? How do you know, which watchers should be automatically set there? Thanks.

Hi @Tony Styles , my pleasure :-)... Thank you and have a great day too!

Thank you! I think the problem is in the "Link Issue to" part. Please, select "Trigger Issue" instead of "Most recently created issue". Trigger issue is the issue, which has been changed. Most recently created issue is empty in this context, that's why you get the error message.

Hi @Tony Styles , this is a little bit strange... would you please share me the screenshots of your configuration and audit log? 

Hi @Tony Styles , thank you! please try something like this: When: * Field value changed - Fields to monitor for changes: Person number Branch rule / related issues: * Type of related issues: JQL * JQL: "Person number" ~ "{{triggerIssue.Person number}}" Then: * Link issues * choose appropriate link type

Hi @Tony Styles , let's imagine you have 5 issues with the same Person number. Then another issue is updated with the same Person number. You should be able to find all the five issues and link them to the sixth, but will this be the correct result? First five issues will be linked to the sixth issue, but there will be no…

Hi @高田翔暉 , welcome to the Atlassian Community! I've tried to used translator, but I'm not sure, what you are asking... Would you please share some screenshots, hopefully it will help me to understand. Thank you!

Hi @James Sanders , you should be able to do something like: {{now.plusBusinessDays(3).withHour(8).withMinute(0)}} See here for more information.

Hi, you are working with two projects, so I don't think it is possible to get this work with only single project rule...

Thank you, now I understand perfectly... but unfortunately I don't think it is possible... There are only existing users in the Reporter field, so you won't be able to select the user before you create account for him. To be honest I can't think of anything, which will improve the process. It would help, if the another…

Hi @Matt Harford , if you are agent in JSM, you should be able to edit Request participants field from the issue's view, which results in sharing the issue with another user. If I don't understand you right, what's the problem, would you please share some screenshots? Thank you!

Hi @Kevin Yi , welcome to the Atlassian community! Please try to look at Insight - Asset Management This application is now standalone, but it will be soon integrated to Jira Service Management, so this will the natural choice for Atlassian solutions...

Hi @Sanny Dominguez , maybe you can use CSV import to update the issues after they are moved to the new project? Field Watchers should be available... Are there any watchers in the issues now? Do you need to completely replace them? Or just add another users? Thank you!