Comments
-
I don't think you will see this. The point of watching is to enable an individual to say "I want to be kept updated", not to enable it to spam some group who probably have members that really do not care.
-
The best option is "an agile solution for Service Desk" - run one JIRA Server with Service Desk and Software applications installed on it. If you have to keep two servers, one for SD and one for Software, then I would look to duplicate the project(s) you need in both. You could rig it up with ScriptRunner, but I would…
-
They are not on the board because they are in a separate system. You'll need to duplicate them over (there are add-ons to help), or use it as intended - on the same server.
-
Have you tried the JIRA macro? It lets you define lists of JIRA issues (or just one) and displays their fields in confluence, with the current content.
-
I'm afraid there's a couple of answers to this because the question is a little unclear. Assumption 1 - you only want to allow a transition - you'll need to find/write a condition that can interrogate the current value of the field and return a yes or no back to the workflow. If you do that, the transition you put the…
-
That's not going to work then. To store data on a Confluence page, you have to edit it. You can use the html macros to put dynamic data on a page, but it's not a lot of use - your users need to edit the page to persist changes. If you want Confluence to behave more like a form based application than a wiki, you'll need…
-
How have you "created a form"?
-
Mmm, well, priority is a system field, global and hence what I said above applies. Same for the other system fields - you'll be able to hide them though.All the custom fields - yes, you can tie them to just the issue types you want them to appear for (i.e. test cases)
-
You'll need to explain what "Test Cases" are here, as they could have special functions created by addons. On the assumption that they are NOT tied to an addon, and they are just basic JIRA issue types: 1) Fields belong to issue types - you can just delete custom fields from the system and it will vanish. System fields…
-
Versions belong to projects, they're not global artefacts, even if you happen to give them the same tag/name. If you need to tie things together with these "job codes", then you either need to use the job-code field you've added (and accept that versions are different by project), or keep the work together in one project,…
-
Unfortunately, there's no easy way to do this, and no documented list I can find. Also, for later versions, there is no "WAR installation route"
-
Oops! I feel your pain, I've done that too. Still, as we know the group was killed off, we can tell you what you're doing now is broadly correct. In more detail: Jira needs a group in order to identify "people who can log in". That's the group you put into the general permissions on the "can use Jira" line. You can use…
-
I don't know, you've not really explained what went wrong, or what changed before. Your approch here might be right for your installation, but it's a little difficult to know because I'm not sure what you have or what you're aiming for.
-
Ok, so what is wrong? Do you know what happened yet? Has the "jira users" group been deleted? What have you got under "global permissions" for the "can log in" line?
-
Ouch though, really does sound broken to me! Although it's quite likely that your data is intact (unless you were using HSQL of course - I've seen that thing lose everthing) Best of luck - and keep asking questions when you're unsure! Do you know what the actual cause is though? Your user base deleted for some reason? Or…
-
We have no idea - it's your installation! Can you remember how you installed it? dbconfig.xml really does live at the "root" of the home directory, so if you set the home to something like /foo/bar/jira, it will be /foo/bar/jira/dbconfig.xml
-
Depends on what you mean by "lost", but you can start by logging in as an administrator - they all have login rights automatically, even if they're not in "jira users". If that gets you in, then you should be able to start undoing the damage. If you've broken the admin groups as well (messing with the database?) then have…
-
It's already "admin only". If your ordinary users can do it, then you've installed the plugin mentioned in the link Udo has mentioned, and you need to reconfigure that!
-
Most of us simply use logrotate on Unix boxes for the logs. For the backups, I tend to simply use a one line "find files over x days old -exec rm {} \;" in cron .
-
Ok, what does it try to autocomplete "sara" to when you start typing it? Also, could you try just using Sara's actual plain login id (it'll be lower case and one word, no spaces)
-
What query are you using and what are the symptoms of "not able to search"? What happens when you try "reporter = dave"? (Assuming dave is one of your users)
-
I'm sorry, that makes no sense at all. Which of the three options is closest to what you are trying to do?
-
I'm not sure I understand what you are looking for here. There are three broad things it might be from what you've said: * To write an addon for JIRA Server to install in it - start at https://developer.atlassian.com/docs/getting-started * To write a Connect addon for Cloud JIRA…
-
I'm afraid not, if you want to upgrade Java, you need to upgrade Jira.
-
Service Desk is licenced the same as all the Atlassian stuff, annually for Server, monthly for Cloud. While the licence is valid, you can call on Atlassian support.
-
If you buy Service Desk, Atlassian will support you, yes.
-
Sorry, I misunderstood. I did not realise that "help desk for JIRA" was a product. I can't tell you much more than the documentation - see http://www.teamlead.ru/display/HFJ/HelpDesk+for+JIRA+vs+JIRA+Service+Desk The add-on makes a plain JIRA a bit more "help desk" like, but does not implement Queues, Reporting, Knowledge…
-
Atlassian don't generally have sales people who do this, they rely on existing customers, partners and experts. What would you like to know about Service Desk? There's plenty of online material, and if that doesn't answer your questions, then feel free to ask here, or maybe engage a local partner/expert
-
Same answer - you're going to get large amounts of pointless rubbish if you try to inflict this on users. Consider doing it properly.
-
Ah, all the wrong answers as usual. If you pre-populate a text field, people will ignore it. If you need it to fulful a certain format, people will overwrite that too. Convert it to a set of fields, leave them blank (unless you genuinely do have solid defaults for them) and set them mandatory to force people to enter them…