Nic Brough -Adaptavist- Expert

I can't tell you more than your networking is not working. All of these errors appear to be down to networks not networking.

Because the database is a disaster, in terms of reporting. And as a Cloud service, it's not something anyone in their right mind wants access to (mainly because it's not usefully reportable.) I'll defer back to my usual example. The question "Show me issue X" - simple, understandable, and in SQL, is 57 joins. 57. joins.…

Your "grid" comes from an app that does not support searches. If you want it to, you will need to ask the providers of the app to support searching.

If it works a second time, that suggests your network is failing to find the site but telling your client computer that it has. You'll need to talk to your DNS admins about that. And it's git that is failing, not Bitbucket.

Log in as an admin and go to the project settings, where you can change the project lead.

What message do you get when you post the message you think Flow is sending to Jira by hand (with a curl or wget)?

Your assumption is correct - the workbox relies on some of the functions that the mobile web app provides. Disabling parts of the mobile app won't work, the workbox is relying looking for the main classes it provides and if any of them are disabled, it will fail. I can only recommend that you re-enable the core plugin and…

Jira has a very strong attitude that you should always be able to point at something that needs to be done and say "this person is the one responsible for it" I completely agree with this. If you name two (or more) people who might be responsible, you have introduced confusion and uncertainty, which is, ultimately, a time…

You have not told us exactly how you are creating the sub-task, or why, but assuming you are creating a subtask on the issue that the post-function is running against, the minimal calls you need are newSubTask.setParentObject(issue) newSubTask.setProjectObject(issue.getProjectObject())…

If you do that, please do not rename "Epic". This breaks some stuff in Jira in subtle ways that you won't spot until it's got quite bad. This is likely to change soon, but at the moment, it causes too many problems.

Cloud does not have licences like this, you'll need to get a new subscription for the target account and shut down the old subscription.

The question remains "what did you change that triggered the sudden increase?" If you can't remember what you did, then I would take a look at the log to see exactly what is going into it. Rapid growth usually indicates something repeatedly failing frequently, and I expecy you will see a lot of the same error over and…

Jira Software only implements Epic -> Task -> Sub-task. You can get more layers with Portfolio for Jira, Jira Align or Structure for Jira. There's some other stuff you might look at, but those are the only three fully intended to create more layers over Epic

You will need to explain what you are trying to do in more detail. We don't know what you are sharing, what you are trying to restrict or what does not work.

Take a step back. On Cloud, you do not have licences, you are buying a service. There is no "move licence from one account to another" You will need to start a new subscription (licence) for the new system and then shut down the old one.

What do you mean by "report"? Have you simply searched for issues?

The mail box you use for incoming mail must be a proper mail box, not a shared distrubution list.

You say "I need to remove duplicated issue keys [from a search result]" Actually, no, you do not. Jira already de-duplicates the list. You are not getting the same issue key in the results. The only way you might, which is rare, is when you have a very badly damaged index. If that is the case, you desperately need to find…

I am sorry, I know this is going to sound bad, but could you be clear on which one you mean? Your question has two subtly different ways to be read, and I am not sure which one you are asking. Are you looking for: * Assignee was changed from somebody/unassigned to you on the 22nd * You were the assignee for part or all of…

I'm afraid we cannot tell you. You have given us no context for the question. If you could explain what you are doing and why, we might be able to help.

I would want to ask why one of your DB admins has changed the name of the column. I'd also question why anyone has any access to the database, you shouldn't be looking at it in most cases.

What do you mean by "grid"? 

I am not clear what the requirement is. Sorting issues by date is simple - add the clause "order by <date field>" to the query. That said, I think I do not understand the rest of the requirement is.

Could you explain what this has to do with Jira Software?

Your build of git was done with (a broken version of) GnuTLS instead of OpenSSL. You'll need to get a working version of git.

The single-click option was added to Jira a long time ago because so many people wanted it! If you don't want to use it, just ignore it. The "edit" option you want is in the menu already, as the old way of updating fields, or being able to edit many at the same time. I think I'm asking what the actual problem is here?

There seems to be only half a requirement here, so I am stuck on what you are looking for. The JQL reporter = nic will list all issues reported by nic. Given that, I am not sure what the rest of your question is looking for. Could you explain more?

To respond to the I'm afraid I'm exactly the opposite of the anti-vaccination fool you compare me with. I work from the information I have, which has lead me to the answer I gave you before. Nothing you've said gives me new information. Jira already fully supports Kanban, that's the point I'm making. If you're doing it…

Jira does not track user activity like that, so there's no way to do it in Jira. You could look at some form of external usage analytics (Google analytics - possibly overkill, or at a very base level, implement access logging on the server side)

Atlassian also lean heavily on their partners to support and expand the user base. Incorporating features from vendors into the product damages the vendor, dieincetivising them from supporting and promoting the products, so Atlassian mostly avoid building their own versions of vendor tools. When there is a strong need to…