Muhammad Ramzan_Atlassian Certified Master_ Expert

Which tasks you are referring here, are those Jira tasks or you have something on Confluence itself ?

There is a rule available in automation library. Please just turned it on. The rule is working based on the link type that is "Duplicate"

That would be awesome and i think your addon will get more attractions to those who integrating service desk with third party like BMC Remedy 

@Michal Patoprsty , unfortunately its not supporting the service desk customers. <?xml version="1.0" encoding="UTF-8" standalone="yes"?><base64AttachmentUploadResult> <errorMessage>Current user does not have EDIT_ISSUES permission for issue with id ISD-2!</errorMessage> <result>ERROR</result></base64AttachmentUploadResult>

Please take some time to look into the script, I just created quickly for you, you might need to do some cleanup , Regarding the above error post call is invoking the logger, it means the logger string is not there. What other errors you facing

these are static errors, you can ignore them

Please check my new answer , i updated your script

@Dan27 , What is happening here, when you crating the issue, on same time you are deleting, on backend the issue is deleted. You need to take care 1- Delete the issue in new thread 2- Execute the script with a specific user which you confirmed have delete rights 3- Creating a new thread in Jira is tricky. I have updated…

I would suggest to go with listener , instead of post function.

Keep the key cell empty for sub tasks example IssueType,Key,Parent,Summary Task,New-1,,test task, sub-task,,New-1,,test subtask

Did you execute the JQL query in issue navigator and validate what it returning there?

Unfortunately no, you have to go for a third party plugins. like ScriptRunner, JQL Search Extensions for Jira & reports Here is the example of JQL Search Extensions for Jira & reports, I have this plugin so i can give this example. Please let me know if its helpful. issue in allIssuesInEpic("labels="your epic label")…

Unfortunately till now , no luck without plugins. Just updating my answer, here is the plugin JQL Search Extensions for Jira & reports example if interested to use type = story and subtasksCount < 1

This will not work you can rephrase it as Epic link in (epiclink1,epiclink2) With default JQL , you can get results by mentioning the epic links itself. If you want to get issues results as you required then you need to use a third party plugin like JQL Search Extensions for Jira & reports issue in…

you need a third party plugin like scriptrunner or JQL Search Extensions for Jira & reports Get all linked tickets to ops, if you want not linked with ops then project!=ops issue in linkedBy("project=ops)

you can achieve with two steps. 1 - search the stories with empty label belongs one the required epic , example Epiclink=abc and label is empty It will get all stories with empty label belongs to epic abc 2 - Now perform the bulk operation and update the story label.

Are you talking about ops issues and their linked issues?

You cannot achieve it by built in queries, you need a third party plugin like scriptrunner or JQL Search Extensions for Jira & reports Example following will get all issues where your curernt issue lable=abc and linked issues label=abc issue in linkedBy(label=abc") and label=abc Reference:…

As mentioned by Fazila, you can use third party plugins to achieve like ScriptRunner, JQL Search Extensions for Jira & reports I am using JQL Search Extensions for Jira & reports and here is the example how you can achieve your results. CommentedBetween can be used to find issues with comments added between particular…

There could be two reasons. 1- You don't have manage sprint permissions 2- You have manage sprint permissions on the current project but , your sprint have issues from another project where you don't have have the manage sprint issues . please execute this query sprint = "SprintName/ID" and project!= the current project If…

If you provide little more information,we can help you in better way. What i understand is she can only see the most recent which means she can see issues but not sure where is the issue you talking about. Did you try to change the filters?

You might need to use some JQL plugins like JQL Search Extensions for Jira & reports Here is example how to use the query Find issues which are blocked by issues from project JQL with priority = Highest. issue in linkedBy("is blocked by", "is related to", "project = JQL AND priority = Highest") Reference:…

@desarrollo , you are welcome, happy to see your problem is resolved too.

@desarrollo The reason behind this error was weird. I was using a listener which was updating the issue type and that issue type have some mandatory fields. I disabled that listener. But i am still surprised, it shouldn't impact the mail handler, as listener was being executed after issue is created and mail handler runs…

The reason behind this error was weird. I was using a listener which was updating the issue type and that issue type have some mandatory fields. I disabled that listener. But i am still surprised, it shouldn't impact the mail handler, as listener was being executed after issue is created and mail handler runs before issue…

You cannot achieve this without using a third party plugin. I can suggest you ScriptRunner or JQL Search Extensions for Jira & reports Scriptrunner is more expensive than JQL Search Extensions for Jira & reports after 25 users. Here is the example how to get all sub tasks belongs to issue type story using JQL Search…

I am also getting null by using your code, everything is correct issue id , field id. I am surprised for one field its returning value For one drop down field its returning all values not the selected one for all other fields its returning null

Thank you , you saved my life :) 

Hi Joshua Yamdogo @ Adaptavist , I am running my local instance at localhost, previously i was able to send emails through the script but now its throwing the same error as mentioned above. Could you please advise import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.mail.Email…

You can achieve this by using some third party plugins. I am using JQL Search Extensions for Jira & reports and can give you some examples. CommentedAfter can be used to find issues with comments added after particular date. Expected date format is yyyy-MM-dd (year dash month dash day of the month) or dd-MM-YYYY issue in…