Comments
-
You have not explained what you have done to "restore" this data, but my best guess is that you reloaded a database and then tried to use it as the back-end of a more recent JIRA. If that's right, then try running a complete re-index of JIRA. Run the full "lock JIRA, it will be unusable while I run" option. That should…
-
Short answer is that you can't. The longer answer is that you'll need to hack some code, potentially quite a lot of it. There's a bit of a discussion on it at https://answers.atlassian.com/questions/65731/how-can-i-disable-the-greenhopper-for-some-users-groups-roles , although that does wander off into stuff that's more…
-
Short answer is that you can't. The longer answer is that you'll need to hack some code, potentially quite a lot of it. There's a bit of a discussion on it at https://answers.atlassian.com/questions/65731/how-can-i-disable-the-greenhopper-for-some-users-groups-roles , although that does wander off into stuff that's more…
-
Commenting doesn't have the facility to add other fields as you do it, it really is just a comment box for entering comments. I understand you want to send mail on comments now, but I don't really understand the rest of it. Anyway, what you *should* do is look at your notification scheme. That determines who gets emailed…
-
I'm sorry, that makes absolutely no sense to me. 1. Where are you looking? There are several places that you can get a project list, so which one is it? What are you trying to actually achieve there? 2. I can't even guess what you're talking about here.
-
Ok, so you are using OnDemand. As I already said, you cannot set the SMTP server.
-
Are you using OnDemand? Where you can't change the SMTP details? Your second question is just a matter of getting the notification schemes for your projects correct - when someone comments on an issue, tell it to notify the people who should get email for it.
-
They will be buried in the application installation. Some of them may be bundled into system add-ons, which means you'll have to unpack them to get at the templates.I can't give you the exact locations - it varies between versions, and I've never changed the templates for anything other than custom fields, subscriptions…
-
You'd need to hack the templates that are rendering the drop-downs in the core code of JIRA
-
Not in the way you describe "main". The problem is that "issue view" is a mass of different things entwined together, and the current Jira "screen" is just one part of it. You can work it out, but you'll have to do it via standard config. First, you need to work out the mode - are you viewing an issue, editing it, creating…
-
Select "Key" from the list of fields.
-
Oh, I know - the open approach can lead to wiki-tennis with pages being "corrected" backwards and forwards instead of people actually talking, but I've found trying to enforce an authorisation process on a wiki just tells me our collaberators, well, aren't collaberating. I'd try to handle that with a light touch to begin…
-
The wiki-purist in me says you've misunderstood what a wiki is for. Most of the Confluence users I know simply dive in and make the changes they think they need. If someone else disagrees, that sparks a (non-Confluence) conversation about why it's wrong.
-
Obviously, you should always change a keystore password.
-
Er, we have no idea. Jira needs to know what the password you have set on your keystore. If you don't know it, then contact whoever set it up for you. If you don't have a keystore, or you don't know the password, you'll have to create a new one and use that. Have a look at…
-
Duplicate of https://answers.atlassian.com/questions/52491602 (But the image works on that one)
-
There are four types of link I think you might be talking about: * Self referential, where Confluence is pointing to stuff inside itself. Confluence uses its "base url" to generate most of the urls it refers to internally, so check that first (Admin -> General config) * Linked applications, where Confluence is referring to…
-
Ah, ok. You are using Core - JIRA Software and Service Desk run as applications on top of it. But, your licences for them entitle your users to use Core automatically, so you don't need to think about it. To remove the trial licence, blank it out.
-
Yep, just paste your new commercial licence key over the old trial in Admin -> Licence
-
As I said already, the workflow engine in JIRA is closely tied to issues. To do workflow on something that is not an issue you have two options1) Write your own workflow engine2) Rewrite JIRA so it can use workflow on things that aren't issues - this is not something you can do in an add-on
-
The workflow engine in JIRA is closely tied to issues. Your "entity" will almost have to be an issue to be able to use the workflow stuff in JIRA, so you might as well just define a new issue type for it.
-
I'd suggest that rather than ranting here, you talk to Atlassian. I strongly suspect that they have every right to delete your data the moment your support expires (so, yes, they CAN "delete other people's BUSINESS DATA", and you already admit that they DID warn you, so I'd say you're on a hiding to nothing on that front).…
-
You could also have the target pages just use the include macro to pull in the whole pageIt's slightly easier than the excerpt macro because you don't have to put anything on the source page.Another option on the "click here to edit" link might be to use guidance text instead, so that when the user clicks "edit" then they…
-
So you filter for "was reviewed, now in assigned", as that defines a failure. I think your definition of failure isn't quite right though. I think what you actually mean is "has been in reviewed, then went to assigned, and is now in any other status" You can't search for transitions, and even if you could, you'll still…
-
It's not clear to me how you are identifying or defining issues as "failed"?
-
It's proportional to the number of issues, and how fast your server is (mostly disk access), and your version of Jira (later = faster). It needs to read every issue and recreate the index entry for them! On a 2.4GHz quad core VM test machine on a relatively slow network, Jira 5.1 did 350,000 issues in a shade over an hour…
-
It's the line below - jira.permission.* - that can be used to remove the delete permission while the issue is in that status.
-
Use workflow properties to remove the delete permission on status - https://confluence.atlassian.com/adminjiraserver071/workflow-properties-802592825.html
-
Https://support.atlassian.com I'd recommend asking your questions here though.
-
We are not Atlassian (although many of them do read this site), we are end-users like yourself. Atlassian doesn't do sales calls like this either. You can ask us about the features, or contact a partner/expert.