Nic Brough -Adaptavist- Expert

This suggests a problem with indexing, and it's probably to do with the very last line of code, as that is intended to be used when people have typed/selected something in an edit screen. Try issue.setAssigneeId(userKey)

As an admin, Create a new custom field for it, place it only on "view"screens. and then find or write a listener that can catch "issue assigned" events and set the date field.

No, it does not. I've just tested this to make sure, as you cast some doubts into my mind with that, but sprint = X does return issues as I expected it to. Setup a backlog so that I have a number of issues, of which we're only going to care about AA-1 and AA-2. Create empty sprints sprint-1 and sprint-2 Action Search for…

You don't. Filters find issues, not worklogs or people. I suspect you probably want to be looking at worklog or timesheet reporting. I'm not exactly sure what you are actually looking for. What is the question you are trying to answer with this? I mean is it "show me the issues where Bob logged work" or "show me how much…

Correct - both applications will happily connect to others, whatever the level of licencing on them. I've got one client who is using a $10 Jira Cloud system as an "intake" for a specific project. It's hooked up to their Premium Confluence Cloud and their Jira Data Center, all works fine.

Also just plain project permissions - are you sure you, as a user (not an admin), can see all the projects

I think your blueprint is a good way to do this. I'm assuming the desire is to let your Agents work in the main project without having to worry about "is this an existing customer we should be working with" on every single request. A second project for requests from unknown users makes a lot of sense in that case. Your two…

Welcome to the Atlassian Community! Do you know who the billing contacts are? They are the people who can amend/renew your subscription.

This sounds like your conditions are not working, or there are alternate routes through the workflow. Could you do a couple of things for us? Find an issue that is showing this problem, and 1) Nip into the workflow diagram and give us a screenshot of it 2) Go to the project settings and find the workflow the issue type is…

Jira.permission.<things>.<who> should be set to the "who" you want to use the permission for. For example Jira.permission.<things>.group = Jira-developer-users (people in that group) Jira.permission.<things>.user = Bob (The individual Bob can do this) Jira.permission.<things>.role = Developers (People in the role of…

The requirement is technically clear, but I think I am confused on why you would want to do it this way. Let me try to explain what the implications of this are with an example. Imagine you have 8 issues in your backlog today, and you run your sort at 8am, ending up with a backlog that looks like: * AA-1 * AA-3 * AA-5 *…

Welcome to the Atlassian Community! The filter on your dashboard is set to look only at issue where the assignee is Krishna. The issue you show us is not assigned to Krishna.

This is what it says it is - you do not have permission to see the project, or it has been deleted. You'll need to talk to the administrators of that Jira to either get permission or find out why the project was deleted (ad maybe where you should be looking)

Welcome to the Atlassian Community! Yes, but only by duplicating the work your other dashboards are doing and accumulating it. What "summary data" are you looking for in your main dashboard?

Welcome (back?) to the Atlassian Community! The two project types were renamed/rebranded a few years back. Server/DC style projects are now "Company managed" and Cloud's "Nextgen" are "Team managed"

The short answer is "monitoring" - set something up to monitor your systems and alert when they disappear. We can't help you with that, Atlassian doesn't have a monitoring product (but it does have Statuspage which can help your report on failures) But I would strongly recommend that you stop letting them fail. Investigate…

The short version is "start again". Cloud and Server/DC have fundamentally different app frameworks, and an app for one simply has no way of working on the other. You can probably re-use a lot of logic (and if your connect app is written in a java-like language, possibly code for some the logic as well), but you'll need a…

Groups are a way to group up people. Roles are a way to enable flexibility in who can access which projects, they define persona for the people in that particular project. Groups work, but they become impossible to maintain at any form of scale. I once worked in a place where we had 8 Jira admins. The 3 of us in the UK did…

And when someone raises an issue that you discover that you've already fixed in a released version? You don't want to tell them where it was fixed?

You are absolutely right. Technically, there is a "version cap" - it's the end date on the licence. Your licence entitles you to use any version of Jira Server that was released before the end date. If your licence term has not yet ended, you can use any version of Jira you want with it. I'd want to check the licence key…

Also the Confluence application log (ideally just the bits around where you started the edit and where the CPU dropped back down)

Welcome to the Atlassian Community! We can't actually tell you. There are a number of 2fa options available, and we can't know which one your organisation has chosen! You will need to talk to your administrators, or the people who asked you to use the system.

Um, yes, I already said most of that, and it's not relevant to the question, which is about the Sprint field recording all the sprints an issue has been in so that reports can work. Jira can show you everything in an active sprint - just specify the sprint, or openSprints().

No, the issue keeps its ranking alongside the rest of the issues in the new sprint.

It is instant for internal accounts, but may depend on the frequency of synchronisation for external directories.

Ok, this is a direct contradiction: "... sort the items ... This solution doesn't need changing the sorting by rank option." The rank is the sort order. If you sort the issues in your backlog, then you're re-ranking them. If I've misunderstood your requirement here, could you explain more?

I don't understand why you are constructing such a complex query when you do not need to. Could you write the question you are trying to ask in plain English (not JQL or expressions). Something like "I want a list of all issues that are in this sprint"

There's no easy way to work this out, because the keys that belong to other accounts should not be shared. If you shared the key with someone, you should know who. If you were given the key by someone, then you'll need to ask them. If you have no luck chasing it down, you can raise a support request with Atlassian and they…

Welcome to the Atlassian Community! This is something that needs to go to Atlassian (specifically their billing department). As it is Trello, it would probably be better to go via https://trello.com/contact#/ - use the last option on the page, the others will give you status, documentation or bring you back here.

Welcome to the Atlassian Community! Burndown is a measure of what you did against what you said you would. If you don't put an estimate on an item, there is nothing for the burndown to work with. But, it doesn't have to be story points, you can burn down on any number you want.