Comments
-
That mostly uses "Browse project: Group (anyone)" to provide anonymous access to the projects Atlassian want to be totally open. Obviously, they don't grant the other permissions to "anyone" as they want to track any changes that might be made.
-
Check the permission scheme for the project(s) and look at who can "browse project". It usually says "Role: user", but you'll need to check everything it says if it's any different. For "Role: user" (and other roles), go to the project's users and make user only the client who can should see the project is named in the…
-
Only if the two systems start competing for resources. I'd recommend working out what is causing these "ups and downs", rather than just moving a database service off without knowing that this might help.
-
Matt nails it - the fields are for requests so they don't appear on plain JIRA screens.
-
Search for them, save the filters and use them to report on the issues in dashboard gadgets.
-
They could be owned by another user than root. Sorry, I should have been more clear about that. After checking that, move on to the log files - what do catalina.out and the confluence log say happens when it fails to start?
-
For a business workflow, there's a simple 1:1 mapping with column:status, so yes, I'm afraid you have to change the workflow. Software boards allow many status in a column.
-
Change the permission scheme for the project. There are lines in there related to logging work. Change them so that they only say "assignee"
-
There is no bulk delete, as there's an assumption that admins clean up after themselves as they go.
-
One of the things about boards is that there's a strong need to be able to see the whole width without scrolling. That means wrapping and eventually truncating the text has to be the choice when they get too wide. I'm afraid that the answer is "reduce the number of columns to something more manageable".
-
The usual culprit of this is file ownership. Once you've accidentally started it as root, some files become owned by root, and that stops the dedicated user from being able to write to them. Check the file ownership across the whole installation and home directories.
-
Not that I can see - https://aug.atlassian.com/ is always a good place to look for AUGs. I'm aware of four Harp mentions (and tries to get to) in Canada, but only Vancouver rings a bell for me in your question. If you don't find one, there's an obvious suggestion - start one! There's lots of resources on my link to help…
-
Solved over at https://community.atlassian.com/t5/HipChat-discussions/password/td-p/583358 too
-
You've used a validator which is checking current input on the transition, and not the value of the work logged. I'd change it to say "validate that work logged is larger than zero OR time spent is updated"
-
If you mark an issue as done, it's done. If it's in the current active sprint, it will be marked as done, because people need to see it. It's not going to appear in the backlog becasue it's done. I don't know that there's a lot of advice I can give. The system is doing what it's supposed to, so I can only question the need…
-
I don't understand "sub tasks are excluded". If an issue is assigned to you, and your notification scheme says to notify you, it will. It does not look at the issue type, it's irrelevant.
-
In both cases, you can use the "convert to (sub-)task type" in the tools menu on the issue view (look for the ... to the right, it's a menu for adding links, cloning, converting and so-on)
-
Go into the space, use "space tools" and then look for the "attachment" tab, which lists all the attachments in the space.
-
Yes, that's correct, the issue status has been changed, so the board shows you the new status. I'm not sure why that is a problem, although it suggests the workflow is not quite right.
-
I suspect the Request Type and Organisations fields are the ones provided by Service Desk, so they apply on the front-end for customers, and not necessarily on the issue for plain JIRA users.
-
It's because date and time are stored in, well, date/time format. Not the "pretty" format that JIRA displays and accepts input in. Even if it returned a pretty date format, a simple ">" is not going to understand it. And you have not told it what your 1d is relative to either. I can't remember if the return value is…
-
Create a new role such as "developer worklog only" and add that to the permission scheme, giving it "browse project", "create issue" and "log work" only. You can't limit people to issue types though.
-
It is impossible to know. You have not told us * which Atlassian application you are building for, * whether the aim is to track it in that application and publish this thing, or draw the tracker into the application
-
Yes, you need a new field configuration, unless you want to hide the fields everywhere the existing configuration is used.
-
You'll need to hack the core code to do this. The message is built into a language file, so you should just change that. Given the annoyance of having to unpack the files, find it, edit it, repack the files and redeploy on every migration and upgrade, I'd question if the effort is worth it.
-
You'll probably need to explain what "top team" does and what you want from an "integration"
-
Have a look at the top of the filter results - there are a number of export functions in there, all of which support custom fields.
-
You need to re-check the permissions for the group in the space, and maybe explain what "can't get to the space" means - is it listed in the spaces drop down for example?
-
Code. There are a number of add-ons that can help you with more clever project creation routines, but there is nothing built into JIRA natively.
-
Maarten - probably saw it on "Answers". Or OSQA, or Jive. I've been rattling it off here as a standard setup since JIRA 3.0.3 was released! But 1. I stole it from Neal Applebaum or Matt Doar, and other people have posted it too. 2. If you're on JIRA 6 or lower, it won't work - it needs the "reporter browse" thing enabled.…