Comments
-
That is not what I asked about, (and even if it was, it tells us nothing because you don't say which Atlassian web App it is) You need to tell us how you are handling test-cases in Jira? Natively? With an App? With an integration to something external?
-
The version of Cloud doesn't matter to us end-users, you can just assume "latest". As your server is 7.13, you're ready to migrate from that.
-
Server is the service that is running - in this case, Jira. Client is something that connects to it to use it (usually a browser) You say you have configured as per Atlassian recommendation, but the error you are getting is almost certainly telling you that you have not. Could you explain all of your configuration?…
-
I suspect there's several reasons that Atlassian don't do this. I can think of a couple, but there are almost certainly others, and I'd like an Atlassian to comment too. * My first thought is that there are some add-ons that do this sort of reporting. Atlassian mostly (but not always) don't add features that are already…
-
Nor am I - I just answered the question without judging why they were asking. Story points on sub-tasks won't work for Scrum. Well, not without code, and even then, it won't do what most people think - as you say "there is no 'partial', a story is done, or it is not. So the story points on sub-tasks don't matter to…
-
Resolution is not really "mandatory" like other fields. You can set it as such in the field configurations like other fields, but then you have to set a resolution when creating an issue! Generally, resolution is technically optional in Jira terms. You don't have to set one when editing or transitioning. But, there are two…
-
Enter the estimates on the stories. Scrum only looks at the Story estimates because there is no partially done concept - an issue is either complete (so it can be burned down) or it is not (so it's open and can't count). Sub-tasks are irrelevant in burn-down, so Jira ignores them. (There are uses for estimates at sub-task…
-
The format you've put in the question is not familiar to me, I'm used to seeing people ask for numbers to come out in their local language format (e.g. in English and US English, we have the format you are converting from, but in Spanish, you'd see 12.345,67) If it is a valid format for a country (probably is), then return…
-
Are you on server or cloud?
-
You'd need to have separate status if you want to have two separate meanings and columns.
-
Log in as an admin, go to Admin -> Add-ons -> Find new add-ons
-
You'll need to do the formatting in your code, then just put $value into the template (or change the template to text)
-
Eh? It's still working here on 7.13
-
If they don't need to know who can be set as an approver, then I'd skip the field completely and write a short script that sets it for them.
-
Go to http://my.atlassian.com/product and look at the list of things where you are named as a contact. Go into each one and either add someone else as the owner and remove yourself, or shut it down. You will then be able to delete your account.
-
It doesn't matter about "could not transition" - having a stack of issues that appear blocked (but report accurately) is a LOT better than having the same stack of issues report complete nonsense, and when you've fixed the root-cause, go on to need some quite complex fixing. Given your screenshots (which are great because…
-
I am sorry, but no, not really. The gadget is good at what it was built for, but your data is inconsistent and not going to feed it the right information, so it fails the reporting. There's no way to "fix" the old issues without hacking the database, which I can't recommend, so the only thing I can really suggest is adding…
-
>I've had to create a (fake) resolution of "continue" to allow these transitions to be satisfied. ARGH, no, get rid of that NOW. You are resolving open issues when you do that. Jira sees them as resolved, so all your reports are going to break. Go to the transition screen on this transition and remove the resolution from…
-
ms-<something> is not a valid uri protocol, it's a botch by MS that is not part of the standards. You'll need to botch code into Jira to misrepresent it as such, as well as get standard browsers to recognise it.
-
Your suggestion is correct. The resolution is all that matters to Jira (Software is a bit different though) - if it is empty, it displays "unresolved" and treats the issue as though it is unresolved. If it has a value, it displays that value and treats the issue as done. There's no way to configure the chart, it works off…
-
The server-to-cloud migration doc used to specifically state that you must export from a very recent version of the software. It now only "recommends being on the latest version", but it really does mean you should be on a very recent version - at the very least, one that is not past end of life, and I wouldn't currently…
-
No, the estimate field is an estimate of an elapsed time. You can simply swap to using a numeric field, which can then hold any numbers you want. But that won't be limited to Fibonacci-ish - you'd need to persuade your users to do it properly. (I say "ish" because most of us break the sequence at 21 and 36 and go with 20…
-
It sounds like the filtering is being done on all possible users, but when you restrict the list, it's not limiting the filtering to the current possible list. Feels like a bug to me. What's the version of Jira?
-
No, text fields won't work. A text field is free text, which makes it pointless to count - all you'd ever get is 1 point per issue. You immediately run into problems like nic != Nic != niC != nick != Nick and so-on. If you're trying to count text field entries like this, the problem is not so much the gadget, but that…
-
Ok, you've checked antivirus, so not that, but have you * checked the date/time on server and client are very close * tried clearing the chrome caches* SSL state (hidden in settings -> proxy -> "clear ssl state") * Browsing history * Are you using an insecure protocol on the server, like TLS 1.0 and 1.1? Once you've run…
-
You don't want to restrict it in "where's my field" - the whole point of that function is to tell you why a field is not there, and one of the reasons for a missing field is "hidden by field config" In the search, there's no way to do this either. Unlike doing it in the "where's my field", it would be useful to restrict by…
-
I'll answer this backwards, as it's quicker if you have background. Confluence has a list of users it can see. This list can be a lot larger than "who can use it", and can be drawn from many places, including LDAP (And when you use LDAP, you can specify stuff like "we have 45,000 people in LDAP, but only show these 2870 to…
-
Atlassian (Cloud) accounts do not belong to you, they belong to the user, so if the details are wrong on any account, it is up to the user to correct them. It has to be this way, otherwise you're opening your system to undesirable change. If I am an admin on a system that has a user that is also on yours, and I changed…
-
I am sorry, we can't tell you anything more than "the code you have in Polarion trying to use the JRJC is broken". It's asking the JRJC to something it does not have support for. Without the code that is broken, we can't tell you where to look.
-
This is mostly the use-case for a "scripted field" in Scriptrunner. Scripted fields do not appear on "edit" type screens (Create, Edit or transition), so it appears on issue view of any type, in the search, issue navigator, reports and so-on. They take whatever data you want to calculate from, perform some logic and store…