Comments
-
That's the point - Status is "stattable", you can count items. You can build pie charts with open and closed.
-
Many gadgets require "stattable fields" - that is, they're unique, countable objects, so you can say "here's 4 X, 5 Y and 3 Z" Epic links are not like that. There's an open-ended list of Epics that might occur, not a fixed list, and the links are all unique. That is, if you try to count Epics, you'll only ever get "1" as a…
-
Import from CSV, or using a script against the REST interface, and some addons allow this sort of thing.
-
You definitely need some sort of scheduler to be able to do this. The Scheduler plugin is an option of course, but I cheat. Almost everywhere I work, I've got access to a unix-like server (often just "the Linux machine running JIRA") which I can rely on to run scripts. If you can write a simple script that can poke new…
-
I can't find that in the marketplace - could you give us a pointer?
-
Yes, they count towards the licences because they are logins. There's no such thing as a temporary user. You're either a user or you aren't.
-
You can create another group, grant it "can use" and use that to grant access to the space the external users should see. Then make sure the account created for the external person is only in that new group. You could also add them individually, but then they have to be part of a group that "can use" anyway, and you'll be…
-
A pick list wouldn't work anyway. Think of a system where you've got hundreds or more labels...
-
I did not mention global transitions at all. Although I can see my posting didn't explicitly say you have to do this separately for EACH status. I would have mentioned them, if I didn't already know that they wouldn't work, but I apologise for being thoroughly unclear on that! I should know better and been explicit.
-
I don't think there's an easy way to do this. Either a field is available for edit, or it is not. Some thoughts include: Use the "restricted edit" trick. For each status, add a transition to the workflow - one that does not change the status. Make it go through a screen that includes your fields, and put conditions on it…
-
Start at: java.sql.SQLException: Can't create table '#sql-91e_d096' (errno: 13) Usually means your database service doesn't have the correct permissions on the file system to create the files it needs (either temporary directories, log files or, most likely, actual database directories)
-
No, I had a look too, I couldn't see any. I'm not aware of any either.
-
Define "integrate", and check the marketplace.
-
Neither, or either really. The installer installs JIRA. It doesn't care if there are other services running on your server. It's quite common to see people put JIRA + Database + Web Server on the same machine (usually if it's an internal server), and simply call it "the JIRA machine". It's just as common to have JIRA +…
-
It's a fork of OSQA - look for the link to the original open source stuff at the bottom left of this page. It has been suggested that Answers could become an Atlassian product, but I don't know if that is still on the cards or how long it might be.
-
You've set the field "operation categorisation" as mandatory, either in the field configuration, or in a validator in the "create" transition in the workflow. You need to put that field on the "create issue" screen so that the user can fill it in, or make it optional by changing the field config or removing the validator
-
That depends on the config I'm afraid. The trick here is that a "permission scheme" is a set of rules that say "people matching rule A, can do B in this project". So, you need to look at that to find out what the rule is for "Can delete attachments". That rule could say "groups A, B or F", and/or "current assignee of the…
-
Ah, Cloud, sorry. You've missed the big box that says "more has moved over here", as Tom has pointed out.
-
Has someone changed your permissions to do things on the project?
-
I'm afraid not, that's what the docs say you should do, and if /opt/atlassian/application-data/JIRA is the "JIRA home directory", then you've done everything correctly. I'd be expecting to see four workflow items before the "workflow" button appears.
-
It's working in the dev system I've got here. Did you restart JIRA after creating/editing the file?
-
Asking for plugins without telling us what you're currently doing, or how you're already using the built-in stuff is not really a useful question. To get started, look at the built-in time tracking - https://confluence.atlassian.com/display/JIRA/Configuring+Time+Tracking Then head over to the rather handy list at…
-
Yes, validators kick in after the user clicks the button to go on through the transition, and return the user to the screen with an error message on why it's failed validation. That is "accept/deny at update time". You could do some horrid validation with javascript, but I'd recommend avoiding them for the sake of…
-
The standard way to do that is use validators in the workflow - they can check the content of fields and prevent issues moving on if things are incorrect. There's not many distributed with off-the-shelf JIRA, but loads of them in add-ons, and you can write your own with Script Runner
-
It's the same process as 4.3 to 4.2
-
Alex's answer is probably the best approach for downgrading, and his point about official support is important - I have no idea how much the database has changed between 4.2 and 4.3, but he does, so it could be worth a try. I'd still try upgrading the plugins first though. Confluence 4.3 is nicer than 4.2 :-)
-
Yes, you can try that. There's no guarantees, but generally, with a very recent release, the "plugin is not valid for this version" actually means "it might be, but we haven't tested it yet". Manual installation will tell you, but I'd try it in a development system first, and backup the main system before risking it (That…
-
Ah, um, you can't downgrade. You can go back to the last backup you took of the 4.2 system, that's probably the best you can do. You might be able to export everything from 4.3 and re-import it, but I don't think the process of manually downgrading the database is going to work.
-
You need a way to identify "my team". The most simple way to do that is put them all in a group. Lots of reporting functions allow you to search and report by group.
-
No, the change of workflow will only affect the *status* of issues. All the other fields will be untouched.