Nic Brough -Adaptavist- Expert

I'm afraid thre is nothing you can do here. The error message about "history searches do not support statusCategory" is accurate - "changed" only works for a few fields.

Yes, use bulk-edit, select "move" and don't change the target project. Although I suspect I do not understand the question - the action "move" really is for changing the structural things in Jira, for when configuration differences may affect the structure of the issues. "move within a project" is nothing more than "change…

Ok, that's clear. I'm afraid to debug this, there are only two things we can do * Look at Zendesk to see what it is getting from Jira and work out why it is not updating * Read the Jira logs to find out what errors are occurring or being returned by Zendesk. We can't do this ourselves, only Atlassian support have access to…

No, the "issue level security" is the thing that is done at parent level. You will have to handle visibility of the issues with it on that level, not the sub-tasks. But you can set issue security such that "group A can see issues in level 1, group B can see level 2, group C can see both, and group D, none" Issue security…

Post-functions do not run "for status", they run when a transition is executed. What transition is this post-function on? What does it do, and what is it supposed to do?

Yes, Crowd acts as a single directory for your users - you can connect as many applications as you want to it, all of which can then use it for a single source of accounts. You can do much more complex things, but a lot of people use it in the most obvious and simple way. If you get a 200 licence for Crowd, you get 200 for…

You should create a new custom field of type "scripted field", then go into Admin -> Scriptrunner -> scripted fields, and add a script to it. That script should * use CommentManager to get the comments from the issue * Work out which one is last * Return the body of the comment, along with any other data you want from it…

This is not a question we can answer, you have given us no information. A link to a (probably) existing issue in a system we cannot see, with the statement "how to fill issue" is not even a question and there's nothing else to work with. Ignoring the linked issue, to "fill an issue", click create and put in values for all…

From memory, a scripted field that does something like def allComments = CommentManager.getComment(issue) gets you a list of all the comments. What I can't remember is how it is sorted, but if it is by Id of the comments, then just grabbing the last element from it (as lastcomment) should get the comment, then you can say…

No, the visibility of a sub-task is determined by the visibility of its parent issue. You can't hide a sub-task without hiding its parents (and all its siblings). With some trickery in the workflow, you can make the parent task totally unchangable while allowing full access to its sub-tasks (or vice-versa). (Actually,…

I need to take a step back and ask you to give us the numbers again. One of your comments said "Actually, even I checked this, list of issues with 187 results contain several issues with Resolution value as 'Unresolved'" which it should, but suggests you are getting different numbers from each query. So, in one go, could…

See https://confluence.atlassian.com/jiracorecloud/how-do-i-build-the-workflow-i-want-765593066.html

No. The post-functions are part of the transition, Automation works a lot off events, which happen after the post-functions.

Ok, I'm pretty sure I know what is wrong. As an admin, can you go to Admin -> Issues -> Resolutions and look at the list of resolutions you have? Specifically, is there one named "Unresolved"?

Ok, that rules out the thing I was thinking of. But it also leaves us with the next question - what is actually wrong with the report? You get 187 reults that match the first two clauses, and that narrows down to 6 (7 now) when you exclude the resolved issues from it. So what is the actual expectation and where is this…

Yes, sorry, that is true. A sprint goal will include the sprint backlog, otherwise it's not a lot of use though.

Could you get us the count of issues for a third query? (project = "Global Markets IT" OR labels = GM2019) AND Status not in (Cancelled, Closed, "moved to production") AND resolution is empty There are a couple of ways to get this problem, and the count of issues for this third query will rule one out, or strongly suggest…

Are you using a security scheme to hide issues from people? The burndown chart will be calculated using only issues that the current user has access to.

Did you read all the links in the "how to fix this" columns in the error message table?

What does the log say the problem is?

What do you mean by "master-slave configuration"? What are you trying to do here?

Links are stored as markup in text fields, you'll need the Logic app to send markup instead of plain text

No, you have to choose to let people (or robots) into a space. Global permissions are not (and should not be) space permissions. Almost all Confluence installs need to be able to control who can do what by space, not just allow everyone everything.

Makes sense, there's already a migration between workflows in progress, so it's not going to start another one (if it did, it would trash your data). Leave it long enough to finish the current migration and try again (assuming it's not the same migration repeated) If your migration is taking too long though, you may need…

What type of field are you trying to add the link to, and what error message are you getting? Also, what happens when you try to add the link "manually"? (By typing or pasting it into the field in the Jira UI)

Groups cannot be renamed in Confluence.

No, the licence is irrelevant, it only looks at the number of people with active accounts. This is likely to be the configuration of the app or board. Do you see the same when you use a browser to see the standard UI?

So it sounds like you should get Jira and your web application to use a shared user directory. Then people would only need one account to log into both. Jira supports a range of external user directories already, but for Cloud, you'll need to use Google accounts or Atlassian Access.

I'm afraid your screenshot is too small to be readable. Could you give us the text of the warning message? And explain what part of it you do not understand?

As I said before, Cloud URLs are effectively fixed in place.