Comments
-
Do you have the fix version field on the screens for the issue create/edit? And do you have at least one existing version to work with?
-
It sounds like one of your admins has made a field called exposure mandatory, without adding it to the create-issue screen.
-
If you go over your original estimate, then you go over it. It's an accurate record of what happened. The issue is not "done" just because you've reached or exceeded the estimate, it's done when you finish it, no matter the amount of work. I'd recommend simply letting the software record what has happened. As you've…
-
An estimate has to be numeric - I'm not sure how you'd expect a useful estimate to emerge from other types of field (a select list with options of Penguin, Cat and Wombat for example). Using remaining estimate as an estimation metric would be terribly useless as well - the most simple explanation would be that you'd be…
-
Have you created any numeric custom fields for it to work with?
-
The question I'd ask is "why?". What are you trying to achieve here? The permissions in JIRA are heavily wired into the core of JIRA, and you can't just add arbitrary permissions easily. Certainly not in an addon, you need to mess with core files to add the permission. Although you'd be able to use a new one in workflows…
-
Not silly at all! You found something odd, asked for help, and have now worked out what is happening :-)
-
Which plugin is this?
-
Your connection is set up incorrectly, or your network has dropped it.
-
Do not just remove it automatically - it's there to stop you damaging your installation by running two installations simultaneously. You need to find out why it's hanging around and deal with whatever that problem is.
-
The last sentence in there gives the reason - your certificates are not set up correctly. It's either a duff certificate, or, more likely, the certificate authority is not installed right. This happens a lot when people start with certificates. I find the Atlassian docs on it to be quite good, at least for Java based…
-
No tricks, other than follow the docs. But, what errors are you getting? Check the log files for more information on what is wrong.
-
I think it's consistent - if you make any field with options mandatory (component, versions, select lists, etc) and then don't give the project any options, then it's making the point that you have misconfigured it. I don't think it's a bug - there's usually a good reason for making a field mandatory, and you shouldn't be…
-
It's a logical thing. You're thinking in more fuzzy human terms, but you need to be precise when you are talking to computers. The resolution field is either empty or something. When you say "resolution != Fixed", you're thinking "where the resolution is not fixed", but that's not what you've said, because when the…
-
No. You can get some loot by contributing usefully here. You can make money by writing popular add-ons (sadly, not necessarily "good", you only need to meet the criteria that someone is willing to pay for your add-on). . And, of course, you can take a job with Atlassian (or a partner) and get some income that way. None of…
-
It's the percentage of work that has been logged against the issue vs the estimate you made for it.
-
Service Desk does most of that. For a Knowledge base, add Confluence + Questions, and for chat, add hipchat (although that isn't quite a built-in chat portlet type thing you get on some sites)
-
No. This came up a couple of days ago, asked about issue-types, but the same principles apply. See https://answers.atlassian.com/questions/30696/different-resolution-options-according-to-issue-type See also https://jira.atlassian.com/browse/JRA-3821
-
If you can then see the issue without any login, the next step is to be 100% sure there is no "anyone" in the permissions for that one project, then visit https://support.atlassian.com to raise the issue with them. It sounds very broken to me, and quite a security hole, so I'd expect quite a swift response.
-
Completely understand, but I don't share emails in public (so much spam already). Could you try it with a clean browser? If you've got Chrome or Firefox, there's an "anonymous browse" option which will not carry any login details even if you've got a normal session running - that's more than good enough to do this test.
-
Ok, so can you pick up a demo issue and check with a totally anonymous account? Use a browser you've not logged into your Cloud Jira with ever. (You could post it here to get one of us to check it)
-
Change the permission scheme(s). Remove the "group" called "anonymous" from all inappropriate permissions (Frankly, that's all of them other than "browse" for a start, and "browse = anonymous" is only for certain types of public project too)
-
Ok, that helps me understand it. You're effectively double entering an estimate - once in time and once in story points. (Not wonderfully efficient, but that's not the question here. I'd be tempted to remove the estimate field from issue create and script a post-function to set it from the Story Points entered. Or…
-
I think the problem here is we don't know what Jobin is calculating or expecting it to do - there's certainly no relationship between story points and time built into Jira, so that needs explaining as well as the expectations!
-
What do you mean "add estimates together" and "equivalent to"? What calculated field are you using, what is the mathematics you have entered to try do this, and most importantly, what is the actual mathematics you are really aiming for?
-
Jira does not have "project level" fields like this. You could install the "profields" plugin, or write a plugin that does something similar.
-
Your question was quite clear, but It was missing some information that I think effectively got lost in the translation program The key point here is: >we'd like to create new domein (I don't know how to say... but we'd like to start JIRA from zero based, creating our own domein, create users... and so on) That makes…
-
I apologise for my poor language skills, I am relying on a translator program here. It sounds like you have a JIRA instance you want to share. The server is in Japan, but you want to share it with US people. If the service is shown to the internet, then you can simply give your US users accounts and they will be able to…
-
To expand on that... NEVER change a JIRA database while it's running. Even when it's not, you need to have a *total* understanding of what you're doing, and 99% of the cases I've run into where people use SQL writes simply don't. So they end up going back to a backup. Or worse.
-
I've made a mistake - there's an addon in my installation of JIRA 7 showing me a link to view the log.There is no "show log file" option in JIRA. May I ask what makes you think that there is?