Nic Brough -Adaptavist- Expert

How are you defining "Teams"? I ask because plain Jira does not have them. It has groups, and project roles, but not teams. There are apps that add teams (Tempo and Portfolio do something along those lines), and you might be doing something with custom fields, but I don't want to write an essay on every possible meaning…

My guess is that you have set the output template to be a string, but you are returning a number. There are some errors in your loop as well. I would * Move the def customField line to before the loop, you don't need to fetch the field every time (just the contents) * Change the issue.getCustomFieldValue to read the issue…

Could you tell us exactly what type of fields "Url" and "project" are? The names of the type are listed beneath their names in the list of custom fields. Also, could you explain what you mean by "follow"?

It is close enough - you may find the odd one where a lower id is used for a more recent upload, but that will only happen when people hop over each other. If, for example, I start an upload, then you start one, yours completes before mine - I will have the later create date, but the lower ID. It's likely to be seconds or…

I'm afraid Atlassian are quite Agile purists. Sub-tasks are irrelevant to the backlog. A story is either done or it is not. 0% done, 1% done, 99% done - all mean "not done".

Resolution is a global field, but you can limit what your people get offered with Workflow properties 

You'll also need to set up your network to route that hostname correctly for other computers trying to reach your Bitbucket.

No, the issue navigator is part of Jira (the Rank field comes from Software). It has no edit functions, only display and sort.

The first one is eminently reasonable, but the only way to implement that would be to get the project owners to remove you from it. The opt-out option is the one that is never going to happen, because that's the one that breaks the data rules and ownership. This really does come back to having your admins look after the…

I don't have the time to parrot documentation at you. https://confluence.atlassian.com/adminjiracloud/associating-screen-and-issue-operation-mappings-with-an-issue-type-776636504.html is a good starting point for learning how the screens hang together. Please, go to the project and look at the admin section. You will find…

The first thing to do with performance issues is identify what exactly is slow. Page rendering? Admin actions? Editor load? Editor saving a page? Email being received late? REST calls? The timer in the log is telling us nothing more than a status check on Synchrony took 11 seconds. That's not a performance issue, that's…

There are far too many factors to try to feed into an estimate of re-indexing time. A Jira with 1,000,000 issues and 5 custom fields might index faster than one with 100,000 issues and 500 fields. 10 times the number of issues implies 10 times the time, but the fields change the overhead. It's not a simple multiplication…

A query cannot include a deleted issue. There's nothing there to include, a deleted issue is completely gone from the database. I can see why you phrased the question like that, the error message says the parent issue for something is null, which implies it is deleted. It may well be the right guess, in that it is deleted.…

They are sort-of incremental, but not by issue or project. If you look at the pattern of IDs, you'll see it continually increasing, but in small hops. For example, a small Jira I have here has attachment ids like 10400, 10401, 10410, 10420, 10421. I can tell you that each attachment was added in that order - lower numbers…

I think you are misunderstanding "version" here. The version of Confluence has nothing to do with it, Sudhir was referring to versions of the content. Imagine a simple space where you're just starting out. You create 5 pages, blog once, and get 10 comments. This means you have 16 items of content. Next day, you read…

No, you can't do this. Each "child" option in a cascading select belongs to its "parent" option. Keeping a child selected when changing the parent is nonsense, because it would no longer be a valid selection. (Technically, you could get Behaviours to do this on the surface, but then Jira will refuse to save the result…

You are mixing up screens with field settings. They are separate. Start with the field configuration. In here, you have said "make fields X, Y and Z mandatory". Your people must enter data into them when creating them, and the fields cannot be blanked out during edit or transition (they must be filled for the process to…

Scripted fields do not have options, they calculate something and display it to the users. Your desired behaviour is unclear to me, could you describe what the users will see (and do) without worrying about any part of the "how"? What is the question you are trying to answer for your users?

The request to implement something like this has garned no interest, so Atlassian have done nothing.

There is no way to do that, it would require a rewrite of some of the fundamental parts of Jira from the ground up. That isn't going to happen, because there's no perceivable use for it. Could you explain why you think being able to choose underlying ids would be of use, rather than letting the service handle it all for…

Could you explain what this has to do with Atlassian software?

This error s thrown when startup has failed for some reason. You'll need to read the log file to find out what the underlying errors are.

* Jira has dashboard functions built into it, but you'll need your clients to have accounts to enable them to use them * There are lots of ways to prioritise and order issues in Jira, but I'd tend to use "ranking" in the Jira Software option, as that can allow you to order without knowing lots of detail and feed out…

Could you give us the plain text of the errors? The images can't be read.

Yes, you can just remove the sections that refer to service desk objects - skip the organisations and participants blocks of code.

I would have a look at the first apps returned on https://marketplace.atlassian.com/search?hosting=server&product=jira&query=github

Ok, you'll need Atlassian to add you as a billing contact on to the account. I'm afraid you'll need to raise that with support directly Go to https://support.atlassian.com/contact/#/ and select "billing and payments" and then "help with a deactivated site", and fill in as much as you can of the rest!

The "lock" does not matter here, it is locked to prevent you mis-configuring the field. As sukkeong says, all you need to do is add the "epic name" field to the view screen. If I were doing this, I would start with the project, go to its admin section and find the issue type screen scheme it is using, and drilling down…

At present, Jira does not support the renaming of Epics in full. Jira Software itself will handle it ok in the UI, but Some apps will fail as they expect Epics to be called Epic The word Epic is still used in the code, in interfaces, in structural parts of the UI and in returned data. I strongly recommend that you rename…

Portfolio and Structure are the only two ways I know of to implement an initiative level object.