Comments
-
The rank of an issue is an indicator of where the issue is in an ordered list. On its own, out of context, it isn't useful. For example, if I were to tell you the rank of an issue is 85, you wouldn't know how I am numbering or ordering the list, what issues are more or less important to me than this one, how many issues…
-
Yes, 4Gb should be enough - a gig for Jira and Confluence each and leaving the rest for the OS works fine for 4 people here. I don't know about droplets, but the installation on most Linux variants can be as simple as "download, create data directory, run installer".…
-
This is not really an Atlassian problem, just one of housekeeping a build server. But it is one many of us run into a lot. I would recommend trying to work out where the problem is - find an answer to "what is eating all my disk space?" The df command is excellent for telling you overall usage, but it has a far more…
-
I'm afraid the code that reads incoming mail does not capture the sent-to address, so there's no way to use the data in automations or scripts.
-
Sorry, I completely missed the 1GB you said in your question. I should have read more carefully. That's not going to work. Jira (with no apps added) needs at least 768Mb, Confluence 512 and Synchrony (the collaborative editing service Confluence can use) another 512, and you need to have some room for the operating system…
-
I do, yes. I find "white papers" and "case studies" are usually useless, often just a blend of marketing and "this is how we do it (which is not how I want to)". Demos are a little better, but always lack between 50% and 99% of what you need to see. The only good way to see how a piece of software might work for you is to…
-
Ok, narrowing it down to workflow does make it more simple, but it is still unpleasant for us humans, as the workflows are a block of xml You'll need to read cwd_user to get the id for the account, then search every line in the jiraworkflows table for that id, making sure you check that the id refers to a user and not…
-
Whatever is "pulling the report" is getting valid accurate data. The problem is that it is not displaying it in a format you understand. You'll need to write code in whatever is "pulling" to translate it.
-
Does the droplet have at least 4Gb memory?
-
As an admin, check what Admin -> manage apps says and your my.atlassian.com account to check it's still being paid for first. If it's not a blindingly obvious error message or "not paid for" though, we'll need to get in touch with Atlassian support to track down the actual error message
-
Um, see my answer, I'm not going to repeat it.
-
Ok, so how much memory does the process appear to consume? The ps -ef while it runs before failing?
-
It's not self-serving propaganda, it's an explanation of why it is done this way. Stop trying to justify doing it the wrong way and improve the way you think about it.
-
You've given Zapier credentials that are wrong. Auth failures can be caused by all sorts of things, but most of the time, they mean "your username/password is wrong". The second most common one is that the account you are logging in with is no longer valid In both of these cases,a simple check is to log into Jira manually…
-
Or, asking you to make a minor contribution towards spending a lot of time working out what went wrong.
-
What do you mean by "accounts"? Where do you want to "see" them, and what have you set up to do that in the Atlassian domain?
-
>So it basically sounds like the boards represent a team and are used across all the projects the teams share. Am I understand that correctly? You have understood, and stated that so correctly, I'd like to make a minor clarification ("represent a team" would be "represent a team's work") and then steal the statement so I…
-
Change the board filter to include "order by priority". This will disable ranking, so you need to think before you do it (there's an essay question somewhere on community about this), but if it's useful, you should do it, do some refinement, then swap the filter back to rank and re-evaluate them.
-
Just a quick check to get some more info that support might need - can you log in as an admin and go to "manage apps". This should give you a list of plugins/addons/apps. Look for the "questions" one. Is it there at all? If it is, is it enabled or not?
-
Yes. See the link I gave.
-
Yep, you said nothing about updates. My "don't use SQL with Jira" reaction nowadays is as almost instinctive as "I feel thirsty, find a drink". So I always say it! "Deleting a user is not an option" - fantastic, I wish more people understood that! On the down-side, there's no easy way to find where an account might have…
-
That's a horrible way to do this. You'll need to join the name to the ID, then join that on to around 20 different tables, many of which will need another join to work out what it's for, and others will need you to fully understand the code behind the workflow so you can parse the data from the query accurately. And there…
-
Well, no, you can't save broken JQL. Try correcting the incorrect search and saving it.
-
If you could find one, it would not be of any use to you. Jira does not have a SOAP interface. You will need to use the REST API to do this. Start at https://developer.atlassian.com/cloud/jira/platform/rest/v3
-
My understanding is that you can't, as people should have the same view of a queue and the top 50 is the most useful according to the designers.
-
Queues are not filters, they are not affected by the "issues per (issue navigator) page" setting.
-
Status is changed by transitioning issues through the workflow - this is not an "edit" function, as status is not a field, it's a display of where the issue is in the process.
-
JQL is not SQL. It finds issues, it does not have anything to say about what is displayed when you use the JQL (apart from a suggested ordering) You need to look at the configuration of the "report" that you are running the filter through. It's this reporting that chooses what fields to display. The screenshot is missing…
-
Yes, I still recommend the default limit. Cloud has really removed the concern about total space, but the "not a file store" and "struggle to upload/download really big files" things still apply
-
There are so many things this could be, as @Kurt Klinner suggests. The starting point though is to work out what is slow. Use the developer tools in the browser to time what is slow - is it one chunk of javascript execution? Every item comes through slowly? When you say "slow" is it view page or edit or attach or or or...…