Comments
-
It's not stored, so you can't.
-
As per https://www.atlassian.com/software/jira/pricing - $20 a month. Although you say you've already bought it, so I'm not sure why you're going for Cloud too (this will be a separate system)
-
Sorry, that was a bit terse, I didn't mean it to be.
-
Talk to sales @ atlassian dot com.
-
Windows 78? What does the error log say?
-
OK, then it's clear that your Behaviour setup is the problem. You'll need to debug that.
-
Does it work if you remove the behaviour script?
-
Service Desk has always kept customers isolated from each other. The basic setup is that any given customer cannot see other customer's requests. Very early on, the ability to add other individuals to a request so it can be shared with people was added. More recently, "organisations" were added (so you can put individual…
-
Two things to check * Can you get to it locally? On the CentOS machine. If you don't have a gui, then just try a simple wget of the default base url and see if the html you get looks like a login or setup screen * What does the application log say? Files in <confluence-home>/log
-
Nothing changes technically. JIRA continues to work as before, existing add-ons will work as before. New add-ons will work as they're built for it. But you will find add-on authors generally won't update add-ons for unsupported versions, so while an add-on may look as though it's having lots of new stuff added or improved,…
-
First, you need to decide if this is a one-off, or an on-going thing. If it's a one-off, then an administrator can simply type each line in, although for a large or complex list, it might be worth doing it with a jelly script instead (a bit of work in a spreadsheet can be faster) If it's a list that may vary and is held…
-
You'll need to find or write a listener to catch the "work logged" event and automatically transition the issue. I think you're out of luck though - you can't install these on OnDemand and I don't think there's one on the list of approved plugins.
-
You've got two (or more) Confluence instances pointed at your database. You need to shut them both (all) down and start up only the one that should be running.
-
It's easy to change it in the database. The process is: * Stop Jira * Backup your database * Prove the backup works by restoring it on another server and checking your test Jira can use it * Run the SQL in live * Restart Jira * Reindex it The whole point of the API and the structure of the code in Jira is that it isolates…
-
No. Cloud uses an internal directory or Google accounts, and there's no hooks for anything else. That's the only options you have for user accounts on Cloud.
-
Check that the parameters you are giving the macro are correct. If they appear to be correct in edit mode, it's worth a look at the "page source" to see if they are correct in the raw "code" of the page. It might also be worth trying a full re-index.
-
Ah, it's not quite "standalone software". JIRA Service Desk and JIRA Software are both "applications". They both run on the framework provided by JIRA Core. There are three downloads available to make things easier for us (JIRA Software, JIRA Service Desk and JIRA Core), but you can use any one of those three as a base for…
-
Ah, that's actually quite a hard one. Validators happen during the transition, whereas the asterisk is added by Jira core code by the "field configuration" code. You'll need to code in some javascript to add the highlight you need. On every screen you use in the transitions :-(
-
It's a mixed answer. You're fine on the Spaces. If Alice can see space A, Bob can see B and Chuck can see both, then Alice has no knowledge of B, and Bob has no idea about A. What could let you down is the user visibility. If Alice wanted to mention Boba Fett in space A, then she would probably start typing @bo... at which…
-
There's some stuff to ask about admin access and so-on, but the simple answer to the question is for most of your users - no. If a normal user does not have the right to read a space, then they can not see it. They won't get it in the list of spaces, they won't see it in the activity stream and their searches won't give…
-
Sounds like you are using different screens for "Create" and "Edit" - just add the timetracking field to the "Edit" screen as well as create.
-
You need to make sure the time-tracking is on the create/edit screens - https://confluence.atlassian.com/display/JIRA/Configuring+Fields+and+Screens
-
The "field" you need is "original estimate". I use quotes because the field is not quite a simple "field" in the sense that others are. The field is called "Time Tracking" when you are an admin configuring the screens and projects, but it displays different labels and inputs at different times depending on the context.
-
No, I wouldn't assume that - you've already seen the mess "too many admins" can make with a little bit of power, and Atlassian are being cautious about delegation. They are looking at something, but I very much doubt it's going to be "let them do everything". Personally, I'm hoping for project-schemes - administrators…
-
No. It's a deliberate implementation of JIRA Software. When a "simplified workflow" is chosen, the project administrators are able to do what they want with the list of status in their workflows. If you want to stop them doing this, you'll need to take away the simplified workflow. Make a workflow scheme with the…
-
Yes, this does require a code change. You could raise it as a new feature with Atlassian, but I don't think they'll do it (they certainly won't remove the tabs - I remember this functionality being asked for because users were finding a flat list too long and needed it broken down. But they might enable a flat-list option)…
-
It has some basic email handling as standard. See http://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email (unless OnDemand has had it removed for some reason, but I don't think it has, I think all of that stuff is there, although you may need to raise a support call to get the mailbox…
-
It's very bad practice to disable the logs fully. Logs are generated for a reason, and if anything goes wrong, you'll need the information that's been put into them. I'd relocate them to a larger disk to begin with, and then think about turning down the information going in them - the logging and profiling link @Nitram…
-
>For one particular jira-user no transition-buttons That's not the same problem, this problem was about an issue in the data, fixed with the integrity checker. Cloning would be a poor workaround as you're creating new issues and losing the history on the old one.
-
It's the same answer - it's likely to be a corrupt issue status vs issue workflow. The best fix is to run the integrity checker. The other way to fix it is to force JIRA to re-build the data by changing the workflow (either move the issue(s) to a type or project with another workflow, or change the workflow scheme on the…