Comments
-
Which "plugin update" are you doing?
-
You could use components for this, and then automatically assign to component leads.
-
Notifications are driven by events. Events are fired by changes to issues. In this case, workflow is firing events. So, you need to look at each transition, checking what events are fired by the transition (it's on the "post functions" tab) and update the workflow to fire the right events. You can add your own events to be…
-
That has nothing to do with what you asked. I don't know what you actually want here - to do something with transitions or to do something with group assignee (which you cannot do because assignee must be a single user)
-
What do you mean by multiple transitions? You create an issue. That's it, you can't do anything else, there's nothing to transition until you've got an issue to work with.
-
You'll need to read the log file in more detail to see what the problem is. I'd check the versions of Jira, Tomcat and Java are all compatible first though - https://confluence.atlassian.com/display/JIRA/Supported+Platforms
-
I'm not reading the question in quite the way Steve has. Steve has pointed you to a good answer about "stopping people using issue types in a project" But I think you're asking to stop people creating more than one issue of a type. For example, if you add a "project control" issue type, you never want more than one of…
-
Please re-read the error messages you get on the full restore, I don't think you've understood them.
-
As per docs, http://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email That does the basics. For something more advanced/clever, I always reach for the Jira Enhanced Mail Handler plugin (JEMH) first, but you need to have a look at the built-in create and comment stuff before you can move on to…
-
What does "configure the production database snapshot in server.xml" mean? Anyway, it doesn't sound like you've followed the documentation. If you had, it would have asked you what database you want to connect to.
-
First guess - you've gone your profile set to "do NOT email me on my changes" - if that's true, get another account to make a change and see if the email arrives. If that's not it, then, next, go to admin -> mail and try a simple test mail from there and let us know what happens
-
It will work.
-
Change the "workflow scheme". The default one has a really simple "use the jira default workflow for all issue types", but if you define one or more new workflows, you can set up a workflow scheme that says things like "use my first new workflow for sub-tasks and bugs, my second new workflow for stories, and the default…
-
No, the clone functionality in Jira is a simple, flat, non-configurable process. There are a couple of plugins available which control aspects of it ( See https://plugins.atlassian.com/search/with?q=clone&product=jira ), but most people end up having to write something that suits them. The last link on that list is a…
-
The host, username, password and connection settings. You need to check that the named user can log into the database with full read/write access.
-
Ok, the basic OS stuff is ok then. But how do you know that the dbconfig file has the correct settings? How have you tested that?
-
"run a chmod 666" - that's for files, not databases - you wouldn't get as far as a You need to check if the user that JIRA uses to log into and read/write the database has full access to it. Have a look in jira-home/dbconfig.xml to see who that is, and then use an hsql or h2 tool to check access.
-
I've already said you need to use different schemes for different projects - if you're just plonking fields in and not changing the schemes to match what you need, then of course they're going to appear everywhere, you're not separating them properly.Think of objects like workflow, screens and fields as lists of things you…
-
You need to use different schemes for each of the artefacts. Workflow schemes tell projects which workflows to use for each issue type Screens determine which fields are shown to a user at certain times, screen schemes tell you which screens to use for an issue type, and issue type screen schemes tell a project which…
-
Yup, that's a definite error. Atlassian are good at updating the "supported platforms" pages, and I always rely on them. https://confluence.atlassian.com/crucible/supported-platforms-298977375.html states 1.8 is the only supported version. Obviously, someone didn't get around to updating the duplicated information...
-
Um, no, OpenJDK 1.7 is NOT explicitly supported, only OpenJDK 1.8 (and only on Linux). And 1.8 is the latest version of Openjdk. It might not be the one available in your repositories, but it is out.
-
No. If a user has issues assigned or is the reporter, they cannot be deleted. You could edit the issues and swap reporter/assignee to another user, but most people don't delete users. Generally, you just remove them from all roles and groups, and set their email to a dummy null one. That way you've got a full, clear…
-
Um, what's a "migration request"? Could you explain?
-
We don't know - it was your system, and we don't know what your migration request was about. Could you explain further please?
-
Correct - the message fields are for displaying a fixed message, rather than the content of the field - that's just ignored. If you want different text on screen, put your data in a "read only text" field. But remember as it's read-only, it will only appear on issue view.
-
I think *every* single time I've configured one of these fields, I've put my text in the description, not found it, then gone "oh, yes, I need to put it in the default. I'm sure I'll remember it next time" (of course, I don't)
-
Ok cool, a transition screen is an "edit" type screen, so only the "for edit" one will work there. The text you want on screen needs to go in the "default" value for the field - check the context for the field
-
Sorry, that was a bit short. I think the question becomes "what are you doing" so we can try to work out what is failing for you. The obvious one to check is if you're using the right field type on the screens.
-
It works fine on both for me.
-
The read-only field needs data behind it, and this is not what it's for What you need is a different type of field - one that displays a message, not data. This can be done with the "message" fields from the Jira Toolkit, which I seem to remember is included in OnDemand, although you may need to enable it.