Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! The short answer is "no". An app could be providing any number of functions in all sorts of different ways. For you to report on that, you would need to write code (or SQL) for each app. The marketplace currently returns 950 hits for "Confluence Server apps" Of course, it is more complex…

I am sorry, but a couple of vaguely related sentences do not tell us enough about what you are looking for. Could you explain the problem and what you need help with?

Welcome to the Atlassian Community! Epics don't contain other Epics in Jira. How have you implemented this relationship?

You can restrict the page, or keep it in a private place. Admin rights do not mean "can see everything". But Admin rights do mean they can administrate the system - they need to be able to configure spaces and restrictions in order to do their job, so they will always be able to unlock a page for themselves if they need…

Sorry Dave, I was very unclear. The fields are not incompatible, they just are for slightly different things.

Welcome to the Atlassian Community! Could you explain what you think is not correct? (Where you are seeing it, why you think it is wrong, etc)

Not on Cloud (you can do this safely on server with a database hack) All you can do is add a new multi-select list, and migrate the existing data into it, before removing the old field.

Can you be entirely sure that the "create issue in Epic" is leading to creating an issue of the same type in the same project as the one you have tested the plain create for?

Welcome to the Atlassian Community! As a technical point, you should not be trying to do this. Story points are NOT days, and their definition varies between teams. If you're estimating it in time, then please, use a different field - it avoids confusion when people who have done Agile before see "story points" and you…

Company managed projects do not have a backlog. Their boards do. Your description of "I can see reports, issues and components" suggest that there is no board for this project! Or that you can't see it. If that is the case, there should be a boards -> create board option above reports. If that's not there (or you have no…

Welcome to the Atlassian Community! Your issues are not in the last column on the board, so the sprint does not see them as "done"

Some places will display the issue key, especially if the issue is still there.

Correct. At least, not yet. (And you can do some stuff with forms, in some types of project)

I would start with a quick review of the size and usage of stuff. Run a search for each Story Point field and save them. "Story points is not empty" is the best option. That will tell you how much each field is used. If there's no obvious route (like Story Points used 100,000 times and STORY POINTS used 26 times, so the…

Yes, go to your board -> configuration -> estimation and change the estimate statistic - I think the default list is Story points, business value, time estimate, and issue count (you'll find the list actually includes all numeric fields in the system too, and I think it puts issue count last)

Ahh, good to hear! No, it's no longer possible to use javascript in field descriptions - Atlassian have been getting rid of it because it's the wrong way to do stuff, hard to support and usually breaks on upgrade. They stopped allowing execution completely a while ago, but the javascript that had been added to fields…

So, from your system, you can use "ssh ubuntu@x.xxx.xx.xx" and get a command prompt? What is in that user's .ssh directory in their home directory?

Welcome to the Atlassian Community! Could you explain what this has to do with Confluence? Or any Atlassian-related system? Also, when asking for help with a problem, it helps to give a brief description of what is actually wrong - what exactly are you doing, what you expect to happen, what actually happens and what the…

Some communities are invite-only, usually the early-access stuff that Atlassian don't want everyone to see, only volunteers. You'll need to question the person or place that pointed you to it, see if they can let you in, or find someone who can.

I need to point out that you need to be very careful with doing this. There are two points. First, you are assuming that story points are all used the same way by every team. That is, you can rely on 1 story point meaning the same to Team ABC as it does for Team XYZ. Second, you mention rolling up from sub-tasks. This…

I am sorry, I do not understand "same numbers of the issues"? Do you mean each company should have a duplicated issue whenever the other one creates an issue?

The first question is how are you storing the country in Jira? If you want to automate something based on data, Jira has to have that data to work with.

There's no way to change the display, The history is recording a minimum - the unique immutable id of an issue. It might actually not want to be presenting the issue keys as they could be misleading or useless. Imagine you've got these two linked: 48415 ABC-123 49738 DEF-456 Now you delete ABC-123 and move DEF to XYZ-567…

Ah, that's not an error message, that's one of your administrators trying to botch ini clumsy tweaks. Go to the project administration and look for the field configurations, descend into them, and go find the fix version field. Edit it, and blank out the description.

I don't know what the Epic link has to do with this question, but for the rest of it: Go to Admin -> Issues -> Screens and create a new screen. You'll then want to go into the project where you want to use it, and look through the "issue type screeen scheme", identifying which issue types are currently using which "screen…

Yes, quite a lot. The general limitation at the moment is that they are self-contained, and intended for a single team. They are not built to do any cross-team working, beyond that you can issue-link to other projects.

There are three types of account you could be talking about here, and "reporter" has a specific meaning in Jira. Any of the three types of account could be a reporter, but they have different levels of access to the issues and requests: Service Desk Agent - obviously can do anything. Jira User - may be able to see the…

I'm afraid you need to create a company-managed project, then move all your issues into it.

Oooh, good choice there as well. I happen to live a minute's walk from a tea and coffee importer, and generally pick up a different leaf tea every month.

That is, as you said in your question, a Project board. Neither Scrum nor Kanban. You can't yet configure those, they're pretty much hard coded.