Comments
-
You can create issue "create" screens that contain the fields you need to capture in your form. https://confluence.atlassian.com/display/JIRA/Defining+a+Screen
-
A Kanban board is entirely based on a filter, so the easiest way to "connect a project" is to create the board and then go into the board definition and make sure the basic filter says something like "Project = X, Y or Z" It's likely that your message about "not shown" is also related to the board filter. If your board…
-
There's a really dirty and yet elegant trick for this in v3. I don't know if it's valid for 4, I haven't tried it, but the principle should be similar. The downside to this is that it's embedded in the page itself, so it's not an obvious box outside the editing area. Create a user macro with a sensible name like "hidden".…
-
That's not what was being asked, and has been discussed before. A better option is also to use the tiny url, and, more importantly, when inserting links to confluence pages, to use the internal link format (of space and page name) as that follows the pages when they're moved and renamed.
-
It's not going to happen, I had this discussion with an Atlassian last year. The best you're going to get is the use of the tinyurl option.
-
http://httpd.apache.org/docs/2.2/rewrite/
-
Not really. Confluence serves up it's page names in a human-friendly view where it can. You would need to do some significant coding in the core of Confluence to tell it to be less friendly, or try to rewrite any outgoing urls as they go out through Apache (or other web server)
-
Subscriptions don't support other formats, so I'm afraid you can't get tables or even attachments.
-
Duplicate of https://answers.atlassian.com/questions/12275450
-
Edit the issues and select the version you want them to be in. If you have Agile, you can also drag them in during planning. Note that you have both "affects version" and "fix version".
-
I have a feeling that might be a restricted function on Cloud. Are you on Cloud?
-
Find it in the "new addons" section in JIRA admin, and click install.
-
It's the same answer - click manage watchers on the sub-task
-
Click "manage watchers" when on the issue. It's the number of existing watchers on the view screen. You need to have the "manage watchers" permission for it to be available though.
-
No, you can either edit an issue, or you can't. Only assignee, reporter and fix versions can be limited really.
-
That suggests broken javascript somewhere. Could you get the end user to run a developer tool like firebug to see where it's freezing? Also, does the server side logging tell you anything?
-
Yes, that's why I asked. What are the symptoms of this failure?
-
Does he have the same access to the space as you? Check the space permissions.
-
Ok, the bug was fixed in 5.0 (possibly 4.something high), so it's not the version.However, the transaction isolation level is wrong - it needs to be read-committed - change that in the database while JIRA is offline and restart JIRA, then retry your transitions.
-
Ok, what version of JIRA are you on (older ones have a known issue with this, only fix is to upgrade)?Also, can you check that your database is using Read-committed transaction isolation? That's the usual culprit (although I'd expect similar errors to be appearing in other places)
-
Ouch, that one usually implies you've got something (either inside or outside JIRA) doing something bad in the database. Do you have any post-functions on the transition that is failing? Could you list all of them for us? Also, do you have anything that touches the database in any way? But, first, definitely try…
-
Indexing won't help, it is *only* used for searching and reading, never writing data.
-
You can only assign issues to users that Jira knows are users. You'll need to set them up as users, or possibly import them all from a list.
-
You can keep it really low by turning attachments off, or even just limiting them to smaller sizes. The application installation is a moderately fixed size, the database doesn't really take up vast amounts of space, it's almost always the attachments that grow and chew up the space.
-
On a re-open transition, you should make sure it uses a screen (or doesn't have one at all) that does not include resolution, and clear it with a post-function.
-
Exactly what I said. Look at your workflow. Does it clear the "resolution" field when you use the "reopen" transition from "resolved" to "new"? The tick-flag comes from that field. For more info on workflows and a better explanation that I can give, see https://confluence.atlassian.com/display/JIRA/Configuring+Workflow
-
Does your workflow blank out the "resolution" field when you use "reopen"?
-
Yeah, I think my tone of voice failed to inform my writing on that one. I think it's an explanation of why it's not there, but not that it wouldn't be useful.Head over to https://jira.atlassian.com/browse/JRA/
-
I'd raise it as a new feature, I think it would be useful
-
Because a comment is a comment. Source is not important.