Comments
-
You're confusing "events" with "status". The status of an issue is where it is in a workflow. An "event" is something fired when something changes. There are events like "issue resolved" and "closed" that happen when an issue moves into that status, but these are generated by the *workflow*, not the status. Go to the…
-
You need to import a class to represent the user. I suspect import com.atlassian.jira.user.ApplicationUser is the one you want. I'm assuming JIRA 7 here. Also, getUser is deprecated, so I'd use getUserByName instead.
-
Very Linux. Not sure which distribution at the moment, although if you plough through the docs, it's clear that RedHat/CentOS is the favoured choice, and it's backed with PostGreSQL as the database. I'd say that no one in their right mind uses MS as a server.
-
Ok, it's a similar answer - you'll need to hack the code of the anonymiser, not mess around with the product.
-
It's the same answer - make sure it has a value
-
Ok, so go to admin -> system dashboard and make sure it's got the gadgets for introduction, quick links, voted issues, favourite filters and assigned to me.
-
That's a step forward, the next question is about what you see in the logs when this stuff runs. If it's not updating anything, I'd expect an error message that at least hints at the problem.
-
No, because issues live in projects, and one of the most important things a project does is provide consistent configuration of the behaviour of the contents. I know what you are looking at when you say "bucket" and the simple answer is that you should consider a JIRA project to be the same thing as a bucket in the legacy…
-
Yes, you need to do three things: * Create a field configuration where it you make fix version mandatory * Use that in a field configuration scheme to map it on to issue types * Apply the field configuration scheme to the project(s) where you need the field to be mandatory for that issue type.
-
No, but there's an add-on called "Insight" which can be used to do that. (There are other add-ons too, but Insight is the one I've had the most success with)
-
No. If you remove a group, then it's gone, along with everything it granted. Because it's not there any more. To put new users into a group by default, add them to the "can use" permission in global permissions, then when you add them, they'll take the group
-
There are no restrictions on trials, the software is identical - they just expire and (mostly) stop working. If you have no options on maintaining users, that suggests you might have connected it to an external user directory?
-
Check your profile for "automatic watch" and disable it if you don't want to use it.
-
Use issue security: https://confluence.atlassian.com/adminjiraserver073/configuring-issue-level-security-861253265.html
-
It's using the Lithium board software, which is totally different to Confluence.
-
JIRA refers to things as simple "issues", although there are usually many types, and users can, and do, define their own types. The heirarchy is simple: * Epic * Issue * Sub-task But, for issues and sub-tasks, you can define your own types. Most of us are used to having something like: * Issues: Issue, task, story, bug *…
-
No, they need to be added as a board admin, by an existing board admin.
-
Duplicate of https://community.atlassian.com/t5/Questions/Changing-the-Estimate-statistic-from-Original-Estimate-to-Story/qaq-p/586405
-
Confluence uses the page id when the title would generate a url that is not valid. It does the same with English titles if you put punctuation in them.
-
When you say "it is displayed correctly on the screen, but saved data is " - do you mean it is ok when you type it in, but when you save it and view it later, it comes out as a ?, or do you mean it is a ? in the database?
-
I'm afraid that is probably not fixable. Are you sure you have no backups? Have a look under <jira home>/export
-
That is not priority changes, that is "ranking", and you'd need to write quite a lot of code to implement it safely and cleanly. JIRA doesn't have a field to do that, but JIRA Software implements it.
-
Generally, you don't, you change the remaining estimate and/or log work against it. The original estimate is kept to show you what you first thought!
-
A checkbox is an array of options - consider the list: * Red X * Greeen * Orange X * Blue X There, it's got three options selected, so the value of the field is actually a collection of three. You need to place the option you want into a collection of options to pass into the field, even if you only have one option to…
-
Sounds like you have logged out of JIRA and then started clicking links back into it. Try going to JIRA and re-logging-in. Also, check the urls you have embedded in your sheet - there's a very good chance they're wrong.
-
I don't think your dashboards are the issue. I was talking about the project permissions.
-
You'll need to log in as an admin and edit the workflowto add the properties. Have a look at the sidebar to the left of the link I gave, I think you'll find you're quite deep in the documentation tree, but also beneath something like "working with workflows" which is probably a good starting point for workflow updates.
-
So you mean "workflow". That's easy, although for JIRA systems with lots of projects, maybe a pain to slog through. Choose one "workflow scheme" to be the one that you want to use. Visit the administration section of each project. Change the workflow scheme in use to be the standard one.
-
Again, I can't tell you. I don't know how or where you've installed MySQL or how you've tried to configure it. You need to fix what you have installed.
-
You could do that too, but it's just adding a role that would be specifically used for this. There's no temporary lock, because that's simply not what Atlassian applications are for (unless they decide to find or write a bulletin board or listing application). Admins are expected to look after user behaviour