Nic Brough -Adaptavist- Expert

We need to know what you are looking at really - Community, Confluence or something else? If you give us the url you are using, we can work it out from that. We don't need to know the domain if you have one, it's the <something>.atlassian.net, https://community.atlassian.com or if there's something totally different.

See https://www.atlassian.com/software/jira/pricing?tab=self-managed

Note that "version" in the answer also covers the type of service. From memory, Scroll Viewport is only available for Server and Data Centre, so if you're on Cloud, you won't be offered it by the plugin management functions.

You'd need to amend the code that renders the field in the core of Jira, an app can't help you with this.

You would need to amend code in the application to get the resolution into the tool tip. If this really is a huge problem for you, then I would * Amend the story workflow so that it includes a "won't do" status * Map that status into the "done" column on your boards * Move issues with "won't do" into the new status

The linked issue does all of that. If you want to manage issues in a single project, then don't bother creating linked issues, but remember that you'll need to make all your developers into Service Desk Agents.

No, it doesn't. You don't need anonymous access for customers to use the knowledge base. They get access via their Jira portal accounts.

No, there's no specific timeline for adding any more field support for the was/changed operators. The best we can do at the moment is write code for JQL functions that can be added to support queries - you'll need to write an app to provide them, or use one of the scripting plugins that can create them.

Because it lead the poster to look at the part of the setup that was the problem and they were able to fix it once they'd looked in the right place.

The linked issue does all of that. If you want to manage issues in a single project, then don't bother creating linked issues, but remember that you'll need to make all your developers into Service Desk Agents.

Please see my original answer

Service desk customers won't get those options, a knowledgebase only gives them access to read the articles you've defined as helping for the portal they have come in from.

Jira does not have customisable project level fields. You will need apps to provide them.

Yes, if you're using issues to represent test cases and defects. Take away whatever groups and roles that they have that grant them access to other things, and grant them access to the project(s) your test cases and defects are in

No, Jira only considers the last column on the board as "done". You'll need to put both status in the last column to show that they are done and need no more action.

I think you might have missed some of the context that has gone before. My feeling is that is absurd to assume that when you have several people responsible for something, you can always go to the one that is responsible. This sort of works in a quantum world (which we probably do live in), but that responsibility…

No, Jira generates the issue ids based on the previous number in the project. You can't set them. Off the shelf though, Jira has an "external id" field (not usually exposed by default, but it's not hard to get to, or recreate if it's been removed), and you can import whatever you want into there. Most of us use it for…

I'm sure they will be able to identify the admin account and get your access back one way or another!

There is no way we can help you. We don't know what your Enterprise is, or what iPad app you are talking about. I'm afraid all we can do is advise you to go back to your help desk and ask them again, and to escalate if they're struggling.

Ok, that's great. I'm completely with you on the security, and I am not fond of Atlassian's default "everyone can see everything" approach (even just splitting it into two groups would solve 95% of the problem) The next thing I would do is talk to your Atlassian administrators about setting up the systems so that people…

I am struggling to see what has happened here. "Story vault" doesn't mean anything to me, and so I am not sure what "suddenly turns into trello" means. I don't know who Elise is, or what you are trying to do with this "story vault". I do know what Asana is, but without an understanding of "story vault", I can't really…

As @Daniel Ebers pointed to - https://developer.atlassian.com The javadoc is minimal because there is no need for it to be complex. I've always struggled with some of the links you've mentioned because the docs are trying to talk at every level and hence there's vast amounts of useless (to me) verbiage in there. Docs…

This reads like you have grasped that removing yourself is the wrong thing to do, unless I'm misunderstanding?

Ok, but the lack of settings cog tells us the account you are using is not an administrator.

There's no way to do this - post-functions execute after the data for a transition has been gathered and validated. They have no connection to the UI. Your suggestion of a "sub-task summary" field on the parent issue, exposed during transition and copied later is probably the easiest way to achieve this.

Under site management, you can cancel your subscription(s)

But sprints are not created "inside projects". They're created from boards, which could include many projects. Hence they can't do it. (Although my "fix" would be to get the code to parse the JQL for "project in" or "project =" type clauses so that they can) On the subject of "how many people run cross-project boards", my…

If you log in with the same account you created it with, you should find you have admin rights. If you're using a different account, or can't remember which account you used to create it, then you'll need to get in touch with Atlassian ( https://support.atlassian.com/contact is the start point). They'll want to check some…

You can't do this. A portal has a 1:1 relationship with a project.

You can use Scriptrunner to move issues, but unless you replicate all the checks that Jira does, be aware that you could easily corrupt the issues or have the move fail completely and silently. You'll also need to think very carefully of where you're going to run such a script - you can't do it in a workflow function…