Comments
-
That's one of the factors that feeds into the "Atlassian Verified" badge entries get - accurate flags on the marketplace.
-
SR - What makes you say that? The marketplace entries are what the applications use when the UPM is used to install things or flag them for upgradable. If one is incorrectly labelled as compatible when it's not, then the developer has made a mistake and will probably tell you the same. If one is labelled as incompatible,…
-
The compatibility and availability are shown in the marketplace, behind the links you've already given.
-
Ahh, the "project management" project template is the problem then. Its default "create" screen doesn't have the fields you were missing. So I wasn't far off, I'd just accused the wrong people of removing the fields!Like you, I find that very odd, as I think the defaults should be kept simple and intuitive for new users,…
-
It sounds like one of your admins has removed component, estimate and assignee from the "issue create" screen. Or, possibly, you've disabled them - when you open up the create screen, check the "configure fields" at the top right and make sure they're ticked. (Also the "where's my field" option in there might help you…
-
It's been this way for years, I don't think Atlassian are going to change it. Yet another option with the "split user management" is another line on the table I gave earlier - have a group called JIRA-and-Confluence, which gives access to both.
-
Good point, yes, you can easily do group user is inJIRA accessConfluence accessJIRA usersLogged into JIRAanonymousConfluence usersanonymousLogged into ConfluenceBoth groupsLogged inLogged inNeither groupanonymousanonymous There is one other case as well - if you're using JIRA Service Desk, then you have "customer" accounts…
-
I think it's counter-intuitive because of the implications. Roberto asked this question precisely because it doesn't work the way most of us would naturally expect it to. The requirement is "I want some read-only users to see my space (without using licences)", and the answer is "Enable anonymous access". Nothing wrong…
-
I mostly agree with Roberto here. Whilst the behaviour is technically understandable, it is counter-intuitive and not really that sensible. The reason it is understandable for me is: * Let's say that you have a space that has anonymous access and a single user who is the space admin. * Another user has not logged in, so…
-
Ok, then that takes us straight back to the question of what structures you want to import your data into. We can't really help you with an import unless we know what you're trying to import, and what it is going to end up in. "Test cycles" or "steps" tells us nothing about the target, you need to explain what they are…
-
Ok, so what does XRAY's documentation have to say about imports and how it maps stuff in JIRA?
-
Probably, but it depends on what structures you have setup in JIRA (or test case management add-ons) and what your test steps are currently held in.
-
There's no quick way to add many links to an issue in the UI. You could try a csv import to update existing issues, but if that's no good, you'll have to start coding (I'd use Script Runner to add loads)
-
Ok, you jumped ahead of me, which is good. As the "from scratch" didn't work, the next thing was to check the field configuration, and finally the field context. You got through those two without me. It's not a bug, that's the way it works. You shouldn't need to re-index though!
-
Ok, you've got the right idea, but it is complex. Go to the project header. Look for "screen schemes" and drill down from there. Or, from the ground up: * Create a "screen" with the fields you need on it (call it my-create-screen) * Create a "screen scheme" that says "use my-create-screen for the create process" (call it…
-
No change yet.
-
I've got nothing new.
-
They're looking at it seriously - the biggest client bases are the US, Germany and then the UK, and as it's illegal to hold certain types of data in the US, there's a significant need for one in Europe. I think the UK has lost the deal because the data centre will need to be in the EU to cover the market properly, but they…
-
Not quite, but you're close.The reason I think of it as a two-parter is to keep it simple, and provide breaks. A move and upgrade is potentially quite a long task and if it breaks you're into rolling all the way back. If you do one part first, then if the second one breaks, yo can roll back to the end of the first instead…
-
To start with, break this down into two parts. Moving servers and upgrading JIRA. Work through them both separately, and if you're confident, you can plan to merge the plans https://confluence.atlassian.com/display/JIRA/Migrating+JIRA+to+Another+Server https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA
-
Yes, that's the best way to do it. * Create the screen * Create a new "screen scheme" and set it up so that your new screen is used appropriately (probably all three options - create, edit and view) * Create a new "issue type screen scheme" (you might want to copy the existing one to use as a base). In there, add a new…
-
You can create any sub-task type you want, and use any custom fields on it.
-
No.(p.s. Royce is correct too - trying to do this with javascript won't work because you can still use "move". And since my original answer, more ways to create issues have been generated, so the advice of "don't bother with javascript" is even more true because you need to do it in a lot more places)
-
Yes. In 5 and above, the javascript trick fails. I'm afraid your only real option now is the "break the create". Remove "summary" from the creation screen for that issue type. But please, if you do it like that, seriously chase up a way to put a message on the screen to tell the users that the issue type is deprecated!
-
Yes, there is a slight weakness here - you can't remove an issue type without swapping existing issues of that type to one that will remain. I've seen and tried/used a number of workarounds: You could try javascript to get the users browser to prevent the users selecting the type. Good: consistent interface - the users…
-
You need to separate out the users into logical partitions and set up the projects so that they understand that a person in partition A can't see any projects that don't match. Start at http://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions
-
https://jira.atlassian.com But be aware that Atlassian have closed down similar requests before.
-
No, the workflow only has one "create" point. The best you could do is an automatic transition from the create status to another one, but I'm not sure how you could detect which board was used to trigger the create.
-
Your instincts are absolutely right. Create a project with the Scrum Software Development template, and then amend it (if necessary) to match the processes you want to follow. You don't even need to swap it to a business type. You could also create a business type project, and then flip it to a Scrum, but that won't create…
-
That's a rule imposed by OnDemand settings. You'll need to raise this as an OnDemand support call.