Nic Brough -Adaptavist- Expert

You need to take those sub-tasks you want to use in sprints and promote them to stories - they are not sub-tasks if you want to use them as sprint items.

This is working as intended, as far as Atlassian are concerned. A very cut-down version of a description of scrum is that you have a list of stories that you deliver to a "product owner". A sprint is a time-box, in which you tell your PO that you ar going to complete a collection of stories. These appear in the backlog and…

Hmm, could you collapse/remove the issue view for a wider view of the backlog and sprint? I have a feeling the estimate is getting hidden by a narrower view

It's about different java objects being stored, and objects in java can have very different properties and behaviours. For example, a text field holds a string of characters which works as you would expect. Numeric fields hold simple numbers. These objects are significantly different because you can't do things like…

You would need to rewrite the plugin that provides the gadget (and monitor performance carefully, the limit is there to prevent people having over-slow dashboards and hogging resources away from others)

If the CSV contains an issue key, then Jira will look for a matching issue key and assume the data being imported is an update to that issue. If it can't find one, then it has to assume it's a new issue. For any issue being exported, you need to decide if it is an update in the target system or a new issue, and remove the…

Are you using the new issue view?

I am a bit lost on what you mean there. There is no difference between an inline script and a file based script - when one is called, Jira reads the script from a field or from a file. It's the same block of text however you do it. There is nothing to stop you reading a file in a script, but it won't contain "parameters"…

Jira Core has several business process workflows available off-the-shelf. If you create a new project, there are a long list of project types available, and many of them are business projects, which will set up workflows appropriate for their purpose. You can easily edit these workflows into something closer to your…

An issue is the core element of Jira, it is something that needs doing. They are only accessible to Jira users and are not intended to be seen by customers. A request is a customer-focussed front-end on top of a Jira issue. It is supposed to be the interface between the customer and your organisation, and can have…

No, because Jira Software requires Jira 8.4.1 which mandates Jira Service Desk 4.4.1 See https://confluence.atlassian.com/jiracore/jira-applications-compatibility-matrix-975041287.html for the full range of compatibility combinations.

Yes, you've understood it perfectly. You can only upgrade a licenced Atlassian system to a version released before the end of your current licence. Imagine your current licence ends today (1st October 2019). If you upgrade next week, you can go to any version of the system that is currently download-able, because they came…

"None of them have worked for me" - I am afraid this is of no help. If you can't get Scriptrunner scripts to work, you'll have the same problems with other scripting functions, and quite likely anything else you might try. I would strongly recommend looking again at "has not worked for me" and making it work. We can try to…

Jira has a REST interface as part of it (no extra licence needed) which you can use. Other systems can use it to talk to Jira. Jira also has extension points for webhooks (and post-functions and listeners if you're willing to do some coding), so it can talk to other systems too.

Yes, Jira Software has burndown charts. When a story issue (with an estimate on it) goes into the last column of a scrum board, it is considered "done" and burndown happens then. Note that your "linked tasks" are separate entities, your scrum board will need to include people moving those tasks to "done" as well.

Once. It was a complete fraud, they are just trying scare tactics to get cash out of you. You could try asking for proof, but make sure you ask for something that is absolute. I suspect you will get no reply (or just more threats), because they don't have anything.

You can hide most of the "system" fields with "field configurations" though. Just remember not to hide Summary or Resolution, as that will stop issues working properly.

You can fetch from anywhere really. Workflow functions are all aware of the issue being worked on (and hence most of the system fields directly held on them like summary, resolution, type etc), but you can go fetch custom-fields for them as well. But there is nowhere to store your parameters. If you want the same…

There can be two layers to it. You need to read the conditions on the transitions first, to see what they say. Many of them will say "role: x can do this" or "people with permission y", so you need to read those rules to see if the project permission scheme really is what is driving it. Just because a transition says…

You should visit the "manage plugins" section in admin and work through installing the latest version of each plugin you have.

If you move issues from a Next-gen project to a classic one, then yes, they are going to vanish from the old project (and hence the Next-gen board)

I was trying not to say something like that - I find them particularly pointless myself, there's usually other, better options to show what I'm looking for.

As before, you'll need to correct the settings in the server.xml file.

This means your operating system cannot use its network to get to the database. Sometimes, this is a network problem (could literally be with the network card or any part of the routing from card to service) or it could be a database server problem (if for example, using Oracle with TNSnames that's not set up right)

https://library.adaptavist.com/entity/update-the-value-of-a-custom-field-in-jira might help out

There's not a lot more I can guess at. I would like to see the full error message coming back, but a 401 usually is a simple "account credentials not valid at the other end"

Best thing to do is delete the users from Jira before upload. Jira will only let you delete users where you won't do too much damage to your history (reporter, assignee and commenters)

Ok, that's good, next test is to give Sam the url of the page you are trying to restrict - can they see that page?

I'm afraid we can't help you from just "not working properly". Could you describe the symptoms of "not working"?

Imagine you have a page called "source", and you want to show all of it in another page called "target". Add the macro {include} where you want "source" to appear, and when it asks you what page to include, tell it "source"