Comments
-
Look at the permission scheme first, then have a re-read of the previous answer and comments here - it's all covered there!
-
Ok, so how are you going to tag the issues to mark them as belonging to a team (or set of teams)? You simply can't segregate issues up without some data on them to allow you to do it. The standard approach is to drop them into projects, but you need something else. There are ways to separate them within projects, but…
-
You need to separate out "groups" from "projects" in your head. * A group is a collection of users. A user can be in none, one or many groups (which instantly breaks your access model because everyone is in the "can log in" group and hence can see everyone else's issues). There's nothing in groups beyond "a collection of…
-
Groups don't have all those functions. They really are just collections of Jira user accounts, and have no strong relationships with projects - how you use them is up to you So, taking your points * (project lead stuff in place) * You create groups in user maintenance. Then add the users you want into them * As many or as…
-
This is the same as several other questions you've recently asked. The answer remains "check the issue tracker for Crucible and read the release notes"
-
Ah, I see, you hadn't even created the field yet!
-
Check that it has a "searcher" enabled for it - go to "custom fields" and use "edit" on the field to see that (I prefer the number range searcher) Once you've checked that, you will need to reindex the system before it has any data to work with.
-
That's a networking question. You've not given us an error message, so there's a huge range of things it could be, but to get started, check your firewalls to see if they're allowing remote access to port 8080, then check if IIS thinks it's forwarding traffic between 8080 and your local machine.
-
OK. I can't see another way to do this easily and smoothly. The best I can think of is: * Have a separate project called "customer" * Each issue in there represents one customer, and you can add fields for more information about the customers * You can link issues to customers with the standard link functions But * Links…
-
The fact you've said tags/labels suggests that you're not using the word "customer" to describe a JIRA user account. So the question is what do you actually want a "customer" to be in JIRA? Something on an issue? A project? An issue themselves you can link an issue to? The reason I ask is that the two "standard" ways to…
-
Ahh, well spotted. I must admit, slow pages and hitting firebug is something I forget to do - I've spent so long finding issues with servers, I look there first and firebug ends up pushed down the list when it often should be at the top!
-
My instinctive reaction here is to belt the "firebug" button in my browser and head for the "net" tab, which shows you how long things within a page are taking to load. I suspect you'll find most of the page is quite fast and then one or two elements will be taking far much longer than the rest.
-
If you are on Cloud, check http://status.atlassian.com/ and then raise it with Atlassian support if that does not explain the problem. If you are on Server (you or a 3rd party host it), then contact your administrators.
-
You must be an admin, on page (Admin -> Manage Add ons) and you must NOT be using OnDemand (you can't upload add ons in ondemand)
-
Have a read through https://confluence.atlassian.com/display/CLOUDKB/Changing+the+Cloud+Instance+URL+Address+or+Migrating+to+a+New+Cloud+Instance to begin with - it's pretty much everything you need to know. But give it a shot and come back if you have questions.
-
Swimlanes are the lines across the board you can expland and contract. Have a look in the board configuration for "swimlanes"
-
Looks like you're using stories as swimlanes? If you chose a different swimlane and then set up a quick-filter for "issuetype = story" you could get a board with a good story overview.
-
If your license is still paid up, you can use a "developer license" too - you'll need to nip into your Atlassian account, look for the license and "upgrade" it (the format changes between 3 and 4), then click on the developer license. The only differences between a dev license and your real one is that the developer…
-
Yes. For add-ons, have a look in the marketplace - http://marketplace.atlassian.com/
-
Have a look through https://www.atlassian.com/resources/experts- you can start by narrowing the list down by clicking "hosting". Different hosting companies have different offerings, so you'll need to have a look through them to see what each has available and which might be most suitable. Disclaimer - I currently work for…
-
Migrate off OnDemand to a provider that will allow you to install the script runner or other plugins, or host it yourself.
-
Oh. OnDemand. You're stuck then - I'm not aware of any feature in the plugins in OnDemand that would get you anywhere near this, and you can't install other stuff.
-
Depends on the route you take. Read the documentation for the script runner if you want to go that way. Have a look in the marketplace to see if you can find something that might help. Read the developer documentation if you want to do it yourself.
-
You'll need to find or write a "listener" or "post function" to do this. Whichever one you use, it will need to pick up "sub task closed", read the parent issue, check the status of all the other child issues, then transition the parent to "ready for test" when it detects they're all closed. I'd look at the script-runner…
-
Look at the permission scheme - that will tell you what roles (or other things) can "browse" the issues, and manage the watchers.
-
You don't need any specific role, but you do need to be able to see the issue you want to add yourself to.
-
It's a setting in the "field configuration". I suspect you'll find that your project has a "field configuration scheme" that says "for Issue type 1, use field configuration X, and for all other issue types, use field config Y". If you then look at the field configurations for X and Y, you'll find X has "wiki markup" as the…
-
You are using this plugin https://plugins.atlassian.com/plugin/details/27136 and one of the fields from it that you've configured is failing. You need to go through your list of custom fields looking for one of the four types it provides and check the configuration of them - one of them is configured to calculate something…
-
Yup, go to the workflows and find the one you want to change. Edit it. Look for the transitions within it and click on them. If you're using text mode, it's the lines with ">>>" in them. If you're in diagram mode, it's the lines between steps/status. Once you have one selected, you should have a tab for "post-functions",…
-
The strike-out is simple - if there is a value of any sort in the "resolution" field, the issue is resolved. My best guess is that you have put the resolution on the "edit" screen, or put it on a transition screen so the users set it as they go through the workflow, or possibly used a post-function to set it. When the…