Comments
-
What does the rest of the log say, in the area where the on-screen message is in there?
-
Use a changHistoryManager to get all the changeHistory objects for the issue, searching them for changes to the field. If none are found, the current value is the first use, but if you do find some changes of the field, use the changeHistory that contains the change of field with the earliest date.
-
The burndown charts are generated by calculations using the issue data. There is no "burndown chart data" stored. You will need to retrieve the issues in the sprint, and read them for their estimates and changes of status.
-
That is correct, you've chosen to use a field that works with strings, and that's the right way to order strings. If you want it to behave as a number, you will need to change to using a numeric field.
-
You will need to write code to replace the template functionality that leaves the page title open for the user, and replace the code that allows users to edit the title too.
-
https://confluence.atlassian.com/confkb/how-to-add-a-site-wide-banner-165609599.html is a good example of a global html change.
-
Log into my.atlassian.com , go to licences, and click "new evaluation". If you want access to existing licences, you will need the owner to add you as a technical or billing contact on the licence.
-
You also need to make sure you have the permission to assign issues.
-
What does the log file say the underlying error is?
-
You can't. The keys are stored in a system that is only accessible with an Atlassian account. You either need an account, or to get someone who has one to copy a key and send it to you.
-
@Kevin McCreary- I'm not sure what there is to "disagree" with. Is it the choice Atlassian made not to cost a fortune?
-
There's no licence cost, as long as your licence ends after the release date of the version you want to upgrade to. If your licence has expired, you will need to renew, but then you'll be able to upgrade to any version release before the new end-date. The other cost is the admin's time to perform the upgrade.
-
Actually, no, it does not "suck". A short story: Last week, I spent 2 hours finding and fixing a strange error message for a client. They had done something in Confluence Server that broke a space (not a user macro, but similar). Total accident, one of those things that could happen to anyone. But 2 hours of expense - ok…
-
I'd like to take a step back to answer this one, and look at Scrum first, Jira second, and making it work for you third. Scrum looks at what you deliver during a sprint, not how you do them. You have a list of things to do, agreed and ranked with the product owner, you start a sprint saying "we will deliver these items"…
-
This is something that is quite confusing for a lot of us, but I find the way to think about it is to separate things out one by one. So: We are all clear that an issue is a chunk of data representing "something that needs some attention" * Projects are containers for collections of issues. * That's actually pretty much it…
-
I get them across the top of cards, as patches of different colours, but I'm not a Trello expert, and I don't know if there is some form of configuration that makes those appear (or not) on a card in a board.
-
Nope, assuming the home directory is a standard disk, not a shared disk. (There are bits of Jira you would not want to put on a shared disk like NFS or a SAN). It doesn't care where it is installed, as long as it has space and full permissions on the two directories it's going to use (Jira home and Jira install)
-
The property is purely to allow for translations, if you miss it, the translation won't function. For example, if you've told Jira to show "Machen" if someone has selected German in their profile, then if you remove the property from it, the Germans will see "To Do" instead. And you can always put it back! You can't delete…
-
Not on Cloud. On server, you have some flexibility, in that it is possible to use code hacks or apps that can pre-set it and hide it, but these are not available on Cloud. The closest I've seen is a browser add-on that pre-populated the summary, but you won't get your people to install that globally.
-
An include macro would do this, but you will have to put it on every page - editing every single one you want it on, and persuading your authors to remember to add it (although asking them to use templates can help there) A better option would be to look at your theme - some can be customised to show global things. If…
-
It got spam filtered (best guess is because there was a link in it, but I don't know how the robots think). I've de-spammed it.
-
Sorry for the delay. Yes, removing a duff "to do" will not stop it being re-introduced by a project admin later amending a simplified workflow. This is a bit of a training matter for project admins - you have to persuade them to re-use existing ones as much as possible, and, bluntly, tell them that if they don't, you will…
-
This can help - https://community.atlassian.com/t5/Sourcetree-discussions/How-to-fix-the-Rainbow-Pride-SourceTree-Icon-w-one-Terminal/td-p/1112043
-
Sorry, posted what?
-
The options in the reporter field are controlled by the permission scheme. Anyone who has "create issue" permission will be shown. If you change the permission to just the group you need, that should list only the sub-set of people you want.
-
There's no direct link between them because you've got two Jira systems that are separate services with their own data, and they need to remain separate. What I would do is set up a project in your Jira that mirrors their project configuration (it doesn't have to be exact, but it will be easier if it is close). Then use…
-
You should be able to test for "anything" by just using the phrase without comparison: issue.getResolution() If resolution is empty, this equates to false, and if resolution has any value, it's true. So to get your query, !issue.getResolution() should invert it.
-
You do not. I am afraid you have misunderstood how Atlassian licences work. They are not cumulative (they were, many years ago, but not now), they are tiered. You can't add them together, if you need more licences than your current tier, you have to go up to the next tier. Get in touch with Atlassian licence sales right…
-
What errors are you getting when you log in with a full admin account? Jira usually just goes into a read-only mode when you have too many users, admins specifically can still log in to admin the system (and hence reduce the numbers of users amongst other things) Whatever the error though, if you were to temporarily…
-
You do not. It is not a mail server. Email addresses in Jira are an attribute stored on people's accounts, so Jira knows where to contact them. It can also read email in-boxes in order to create and update issues. But both incoming and outgoing email require email servers to be connected to Jira, and it is those that hold…