Comments
-
Not really, you need them converted to internally supported macros. You might want to try creating user macros to replace them, but I'm not sure they'll give you everything you had before.
-
A trial version simply expires after a while. It's the same software with the same functions as a licenced version. So, yes. Click "create project" and choose the Scrum option
-
Yes, you can use Issue security to lock out access to individual issues in a project.
-
Could your sessions be timing out? That can leave an unused session appearing to be active, but all the functionality disappears from the background and the only way to get it back is to log in again (which you have to prompt it to do with a click on log-out or refreshing the browser)
-
I would say you're going to need some bespoke code and config to do this. Specifically, I would look at 1. Webhooks in JIRA can poke data into other systems over URLs on events. 2. Phire can use JIRA's REST API to read data from JIRA whenever it needs it - not just issues, but searching and so-on 3. Phire can use JIRA's…
-
Only people with project admin rights can add components. You can't disable the on-the-fly addition for them without hacking code to remove it, so the usual answer is "warn your admins that they're getting it wrong".
-
As soap is deprecated and unused in later versions, my memory of it is failing. Part of me wants to suggest using a blank string instead of "null", and also the resolution value is not an array, it's a single value. However, Resolution should not be on an Edit screen either, and SOAP should not be able to edit it if it's…
-
There are two main causes for this problem. First, your base url may be set incorrectly. You need to set this (in general configuration) to the url upon which your users access JIRA. Secondly, if you have the base url set correctly, then you need to check your networking and routing. The JIRA server must be able to go out…
-
What type of database and what do you mean by "integrated authentication"?
-
I suspect they have been added to the internal user directory. You should be able to disable or remove them from admin -> users in Confluence.
-
JIRA - it will take in design requests as issues, track them through their lifecycle (inlcuding ownership), allow collaborations such as comments (and others), and let you report on how they are handled.
-
Simple answer - install JIRA. The REST API is available automatically, and is, in all currently supported versions, a requirement for a good part of the system to work. There's nothing to "enable", it's already there, and you can't turn it off (without hacking core core)
-
You can't. JIRA's structure is Project Category / Project / Issue / Sub-task Project categories are not particularly functional - a project can have only one category and it does not do anything other than group projects together. It's mostly a label for the humans. Epic does give you another layer, but it only does it…
-
Confluence is not designed to be a file store. I'm not sure what you mean by "Confluence project area folder" - is this a webdav directory (which is effectively a Confluence page)?
-
It looks like it doesn't think it's a string.
-
It sounds like one of your administrators either removed it, flipped the project over to a non-Service-Desk type, or Service Desk has expired/been-removed. If it's the second, then you should be able to recover it by getting them to change the project back to the right type. For the third, re-enable or re-licence it.
-
You may have answered your own question here. You need fields, so add custom fields to JIRA. If you are talking about "Service Desk Requests", you will then be able to add them to the request forms.
-
Please, avoid saying "resolution status". They are separate, independent things in JIRA that mean two completely different things. A null resolution is what it suggests - the resolution has not been set. The JIRA GUI has code that says "when empty, display 'unresolved'", but the REST call gives you the actual data of "no…
-
"without a transition" strongly implies an "edit" and hence an "issue updated" event going out to tell us it's been updated. Whilst events contain a list of all changes made, there's no code in the notifications to say "detect change of type X and send mail on that one change". The issue has changed, that's all it can…
-
If you use a standard "get issue", the response includes the history, so you can work it out from there. See https://docs.atlassian.com/jira/REST/server/#api/2/issue-getIssue
-
Code. You would need to find or write a post-function or listener to do that. It sounds like a poor requirement though - if you need this, why are you using JIRA at all?
-
Same problem here. A lot of questions need discussions before they can be answered, and we have no way of knowing when discussions are being made. Email or RSS would solve it for me, but there needs to be proper follow-up notifications for participants, or the questions are just going to hang, unanswered.
-
To move a project from Cloud to Server, you will need to get a backup of Cloud, import it into an empty Server version to create an exportable version of the whole system, then use "project import" to pull in the issues (You could try using the Cloud backup directly, rather than going through an intermediate install, but I…
-
I think you need to talk to your administrators. Points 2 and 3 are config changes your admins make. You'll need their help to find the missing issues as well.
-
You'll probably want to start with the add-ons in the marketplace that can help you with this, or you'll need to be building your own custom connections over the REST interface and using webhooks etc. Try https://marketplace.atlassian.com/search?hosting=cloud&query=TFS You should ideally start with a definition of…
-
The defect ID should really be a string - try a short text field instead.
-
Could you tell us at what exact point the error happens? Committing to the new scheme, or starting to select it etc. We also need to see more of the logged error. I suspect it's a broken workflow though - can you have a look at the one(s) you are switching to and check that all the steps look like sane status (no red…
-
Not at the moment, it's a simple "yes or no" flag, there's no way to have different ones.
-
There's a partial answer. First, yes, you will have to create filters for each person if you want to see "assignee = C" for everyone. It's a fixed question, there's no variables in it. But, there are functions in JIRA searches. Probably the most appropriate here is "current user". If I search for "project = x, issue type =…
-
When you say "hundreds of workflows", that's probably not true. You probably have many different activities involved, but they're more about data items. For a simple example, you might think you have different workflows for "Fix laptop" and "Fix tablet", but the processes involved in doing them are described in the same…