Nic Brough -Adaptavist- Expert

I am not sure where it is coming from either then. If the transition being triggered by "last closed subtask" is giving you a resolution screen from the parent, then I would expect that screen to be the one defined on the parent's transition. Maybe a screenshot of the setup of "close parent on transition" setting here…

Yep, the cPrime Health Report is not coded to ignore them (I'd argue rightly so, as it's worth noting they are there). As for DB Based Jira integrations, you probably shouldn't be doing that. Reporting directly off a Jira database is a terrible thing to do. One of the minor reasons is that it doesn't understand the logic…

So, they are in use. Thank you. The fact is the post-functions are there, so they are being run. I am afraid your understanding of the workflows is wrong. Post-functions are run. What they're for and what they might do, and whether they have internal conditions, we shall probably return to. So, now can we get a description…

The right to move an issue is granted by project permissions. To move an issue, a person must have * Move permission in the source project * Create permission in the target project So, yes, you can restrict movement of issues, but only by stopping people creating issues in the target.

If 1 and 3 are not in use, then why are they in your post-function list? Please, I need to know what the post-function list is in the project/issue type that is affected by this problem. If it is the screenshot that you have given, then 1 and 3 are in use. (And I'm very confused as to why you would keep saying they are not…

As far as I know, there are no plans to allow it to do scrum-that-is-not-scrum with sub-tasks. There was some talk about trying to implement various strategies for configuring sub-tasks, but they went nowhere as "it's a lot of work to implement something that most people won't understand or use or doesn't seem to be right…

Your script is throwing errors because you have not told it to do a lot, and you have got invalid calls in it. I think you have misunderstood the job definition as well. A job is a block of code that runs regularly in Jira. So the misunderstandings here seem to be * The single user the job is asking you to configure is who…

So 1 and 3 are in use in the affected project. I'm confused as to why you said they are not if they are. So, now that we know that they are in use, could you give us the symptoms from one of the broken issues as I described?

The screens column is there in the field configuration just for information. Field configuration is not screens. You will need to edit the screens for the issue types in those projects to get the field added to the issues.

I don't understand. I asked for a list of the post-functions for the issues that are being affected by this problem, and you gave me a list from somewhere totally different? Could you please confirm if the screenshot is from an affected project/issue's workflow, or give us the screenshot from one that actually is affected?

Not really, the problem is that an Epic could contain issues from any project that you could create an issue in. So it's offering you every available type because it can't know what might or might not be valid.

Ok, that mostly looks ok, but I have a doubt about 1 and 3 and would like to look at the exact symptoms. On an issue affected, before the manual re-index, what is the assignee set to, and what does the search return? Feel free to use fake names like: Assignee was Alice before transition, the transition should change it to…

The built-in email handlers simply cannot do that. They are mapped by email address -> project and issue type. They can't process based on anything else. You'll need to have a look at the more advanced mail handler apps in the marketplace, I suspect they may be able to do what you need.

It is safer to simply ignore them, although if you put scriptrunner back, you could write a script to safely remove most of them. Why are you worried about getting rid of them?

Oddly, field descriptions may be held in two places. I'd guess you removed the data from Admin -> Issues -> Custom fields -> That field -> The script might also be lurking in the project data. Go to the project where the issue is still showing it on create and go to project admin -> field configuration scheme -> field…

Burn-down is something that measures progress on delivery of what you committed to doing during a sprint. In scrum, you commit to doing stories, sub-tasks are not mentioned by it. When you use them in scrum, they're a tool for the team to help break up stories into pieces for various reasons (several developers so…

There are no "server" versions of Trello. As far as I know, there are no plans to do it either. The best I think you can do is use the mobile apps for Trello - they can work while you're offline and do a synchronisation when they can reconnect.

Could you show us where you are getting the Server-ID from?

Created and updated are system fields that are calculated for you. "Date closed" cannot be, as Jira does not know what you might consider to be the date an issue was closed - that depends on your process and workflow. If you want to see your version of closed date, you'll need to capture it as part of your workflow, then…

Could you show us the list of post-functions you have on the transition where the indexing appears to be failing?

What type of field is it? And what does "where's my field?" say when you use it from the "configure fields" option at the top right of the create pop-up dialogue?

I think you are missing a "resolve issue" screen on the transition for the parent issue that is triggered when all the subtasks are complete. It's probably got "set resolution to fixed" as a post-function on it instead of using a transition screen.

It's actually a logic problem, not a licence problem. If you don't record who votes in some way, your voting system is completely open to fraud and gaming. To prevent that, the question becomes one of identifying who can vote, and as there's a user system with authentication built into it, so you might as well use that.…

Exactly why I recommend not doing it. You need to understand everything before you can be sure your SQL is going to give you a good answer. With a REST call to the API, you can get any part of, or all, of an issue in a single question, so I'd recommend using that.

Ah, I am sorry, I should have remembered this sooner. & is a delimiter in urls, not a jql operand. Jira is ignoring the bit after the & because it's indicating the end of the JQL! Try project=projectName+and+assignee=currentUser()

You cannot do this - post-functions have no connection to the front end. If you need to give data to the user after a transition, you need to write it back on to the issue. It would be better to use a validator that will prevent the transition if the condition is not met.

Jira sticks to standard Scrum processes - a sub-task is part of its parent, and hence follows into the next sprint, irrespective of the sub-task's completion. The parent issue is what you commit to doing, you don't commit to part of it. If you move sub-tasks between sprints independently of the story, you can't measure…

How did you do the upgrade? The recommended routes don't change the base url. Also, can you describe "can't modify"? Are you missing the option in general configuration's edit mode? It won't accept text? You save it but it goes back?

Hmm, that's not how it is working for me - if I can view something that is restricted, it turns up in the search.

I'm afraid "I can't install" tells us nothing. You will need to explain where you are stuck and what is going wrong.