Comments
-
Ok - >If I click on the 'Add Users' button, it does not allow me to add testuser2 to the group.What error do you get?The global permission for JIRA Users really should be kept simple to begin with, putting a user in jira-users should be sorting it, and it's a nice clear "hey, these people can use JIRA". I'd rather debug…
-
You're nearly there - the Crowd side sounds correct. Although the users and groups are managed in Crowd, each application has permission settings. As an admin, go to JIRA and look at "global permissions". Look for the "Use" or "Can log in" permission (it usually says "must be in group jira-users"). Go back to Crowd and…
-
I'm with Timothy on this one - not only is "Level" not a standard JIRA field, the display implies it's being coded by an addon. A properly implemented custom field addon would mean the field appears in your list of custom fields.
-
If in doubt, you can download the source code for JIRA (if you have a commercial licence). Uncompressed, the source is very very large. An absolutely vast amount of effort has gone into writing it. Trying to replicate something to do even parts of what JIRA is capable of is going to cost you a lot more than a JIRA licence.…
-
That's stirred a memory - that is something very high on the list of things that might be causing a problem!
-
If the mail queue is jamming up, you need to work out why and fix that. Monitoring and flushing it is "plastering over the cracks". What does the log say when the queue stops running? Are there mail server errors? (In some cases, "can't connect to mail server" can cause it to stop dead). Have you enabled mail debugging to…
-
If you put this field on the transition screen, the user will be able to change it, and then the post-function will destroy what they've written. So don't put the field on any transition screens (in fact, it sounds like it should only be put on the issue view sreen)
-
Not even that complex! I'm not familiar with the Apache side of it - all I know is that the config for the virtual servers includes a certificate check before it'll forward any requests - that's nothing to do with Jira. It's off-the-shelf in Apache too, I don't think you need any modules other than standard SSL. We use it…
-
He, actually, yes - x509 certs here bypass login altogether! There's a massive hole in the implementation - there's nothing unique in the certificate to point at and say "this cert identifies this login", but otherwise it works fine. We have an apache front end as a basic gate (no cert, no access), then a dodgy algorithm…
-
The cookbook is for migration because most people want to move off Clear Quest and on to Jira. Ideally, you should choose to drop one of them completely and migrate to the better one. However, to "integrate" them, you need to decide exactly what you mean by "integrate" - it's far too vague a word to start from. "associate…
-
Yes, lots, but none you can install on Cloud that I know of.
-
You'll need code to do this. The code would need to extract users from the role for the current project, and then add them to the multi-user picker that is "tech assignee". I'm afraid you can't add that sort of code to Cloud
-
If it opens on the local machine, then it's running ok. This is going to be a firewall issue - something else is blocking remote access to the machine. Try addressing it by IP address first, if that works, it's a DNS problem. Otherwise it's going to be a firewall, probably on the Jira server, blocking remote access.
-
Assuming you mean the Scrum board, then the fields are on-screen already: The sprint is the current one, by definition, and is located at the far left of the screen, above the board (if it were a Kanban board, the sprint doesn't actually matter, but I suspect it should be an option) The Issue type icon appears on the…
-
Because they're there already in the issue detail view, so you don't need to add them again.
-
I suspect you have put the resolution field on the edit screen. Remove it. The resolution field should ONLY be put on screens where you are moving from an "open" type status to a "resolved/closed" one. That will prevent the problem re-occuring. The best way to fix your data is to close and re-open the issue - the re-open…
-
Very much so, but I'd strongly recommend investing in JIRA Service Desk, not just plain JIRA. JSD is * Aimed squarely at the IT Service Management industry * ITIL certified for service requests, incidents, problems, and change management * Does those off the shelf in the latest version
-
Ok, I suspect your user may have hidden the fields by accident. Look to the top right for the settings and make sure they've selected "all"
-
Odd. What type of field is it?
-
Remove it from screens and hide it in field configuration to be on the safe side. I assume your JIRA is 4.2 or lower at the moment - that's where Labels were added into Jira.
-
You can do your sprints on "remaining points", you just need to put the points in a numeric field and tell the boards to work off that. The important bit is that the "estimate" fields are built for handling times and durations, so that's what they expect as input and what they display. Points are simple dimensionless…
-
Absolutely not. They are completely different fields, because they are measuring different things. An estimate is a length of time. Story points are a measure of complexity and do not have a simple linear relationship with time. If you are finding yourself thinking things like "well, 1 SP takes an hour", then you're not…
-
Sorry, I should really have said that too! First, go to admin -> custom fields and find "story points". Edit the configuration for it and make sure it includes your sub-task types (by default, it only lives on stories I think, so you need to check and update this context) Second, again as an admin, have a look at the…
-
You can put points on sub-tasks, but they won't have anything to do with their parent, so you need to be very careful and rigourous about how you use them.
-
Not with contexts. The context is based on project and issue type. You could use a simple cascading select, or, if you have the Script Runner you mention, there's ways to modify the contents of a list dependent on other fields - https://scriptrunner.adaptavist.com/4.3.1/jira/behaviours-overview.html (although I don't think…
-
I suspect the original poster worked out that they weren't doing the issue type assignment correctly.
-
Ok, I got most of that, but to be clear on the last bit - you go to the workflow scheme, click "add workflow" at the top right, select "bug-task" from both issue type and workflow? Then when you click "ok", you come back to * Bug Workflow * Story Workflow * Default Workflow (default) * Subtask Workflow * ??????? Is that…
-
I'm afraid I'm not understanding the question. Could you tell us what you have in the workflow scheme for the project? For example: * Default: default workflow * Bug: bug workflow * Sub-task: sub-task workflow etc And then explain what you mean by "assigning workflows" - what's going wrong and where?
-
Yes, sorry, I said "numeric searcher" which is pretty much useless because it doens't tell you which search to use!
-
Have you got the searcher set correctly as a number range searcher?