Nic Brough -Adaptavist- Expert

No, this cannot work, it's a logical impossibility, and even if you could do it, an absolute nightmare for your users. Stop trying to do things this way, it's terrible. If "sometime user may forget to update the phase of the issue after changing the field", then fix the process. Stop getting them to change the field, get…

You'll struggle with Epics because plain Jira does not have them. Plain Jira has issues and sub-tasks, so there's only two layers. (Service Desk only really works at the issue level but handles sub-tasks ok). But if you took a Jira system that's been running for a while, you'd need to code for suddenly adding Jira Software…

Because Jira Software only looks at the last column on a board to see if something is "done". Status Category is not the last column on the board (although it is worth matching it up so that it is), it's a categorisation of a status, which might not actually be accurate (frankly, I've yet to see a Jira where the admins…

Bitbucket is a bit different - the data exported from it is metadata about the use of Bitbucket - if you lose a Bitbucket database, yes, you lose that data, but the git repositories with your code are not part of Bitbucket, they're something BB looks after. But, that said, the metadata is still important. I'd look to…

Issues, I'm with you. I'm less sure on watching other people's requests. Why would I want to watch other people's requests? Note - not issues, requests...

That's good. I've re-read my answer and realised I was explaining why it's not there yet (Atlassian's original model of a helpdesk), and missed out that I think it should be added because people are using heldesks to gather feature requests where voting can be useful. I went to that feature request and found I'd already…

Walid was doing bad things to a Server instance. You don't have access to do these bad things to Cloud systems.

They're not fields. Have a look in remotelink (same principle in joining back to jiraissue)

I think you might want to ask this in a Jenkins forum - a lot of us here use it, but may not be at the advanced level you need for knowing much about email aliasing.

You will need an SSO enabled system to do this, one that can be used by Atlassian access and enable SSO in Salesforce as well.

Email is already built in as part of the notifications. So I suspect I am misunderstanding the question. What are you trying to achieve with this?

I'm not aware of any app that could enable this

Customers don't get access to the issues behind their requests. Voting is not something a service desk is expected to do - the core purpose of a service desk is for requesting help, change or bug fixes. It's not intended as a product management system. Customers are automatically watchers on the requests they raise, so…

Yes, you'll be creating a new one and dropping the old. You will lost all your existing data unless you export it though - you're not "changing" anything here, but discarding one and creating another.

Use the UI, the database is the worst possible way to work out how a Jira is configured. It's simply not built for reporting on even issues, let alone config. It's going to take you days to work out queries for all of these and the raw data will mostly leave you completely uninformed and you'll end up simply going back in…

* You can have a single instance for this. You'll need to set it up so that people can only see the project(s) you want them to see (For example, internal users can see projects A, B and C, and external users only have access to C, D and E). I don't understand what you mean by "mapping user" * Yes, you could install 2 Jira…

Yes, you can migrate it with an expired licence. Assuming by "migrate" you mean "move to another server". You'll need to make sure the server ID is carried over from the old install though, and you stop using the old one.

No, Jira has a simple flat "next number in the project" scheme. It would struggle with Epics too, as they only get "stories inside Epics" if you have Jira Software. You would need to rewrite all of Jira and its apps to support a scheme like this. The best you can do is a scripted field that works out such a hierarchy and…

Start at https://marketplace.atlassian.com/

* No, Bitbucket uses whatever the local git version is on the server side * Clients are independent of the server. As long as the client has a version of git that can talk to Bitbucket, it'll work fine. A lot of git versions are inter-compatible, so run your Bitbucket on whatever works best for you and even the really old…

I see no fault here - it's not exactly clear that "document workflow" is mostly what Atlassian would expect a "legal" organisation to look for. They're at a size where they need to be quite generic to keep their broad appeal, but that makes it harder for people with specific requirements (or niches) to find the right…

No, it does not look at the file types. There are some apps that can impose rules and scans, but they're all for Server if I remember correctly. Cloud will accept any attachment (although there are some standard virus/malicious content checks done automatically)

Yes. If you lose the database, you lose your data. If you have not turned off the automatic backups, then you should find some .xml files in <confluence-home>/export - one of them can be used to restore your data. But if that's off and you've lost your database and backups of it, I'm afraid there's nothing left.

You have a field called "Pathway" that has been flagged as mandatory in the field configuration for that project and issue type. You'll either need to get it set to optional, or put it on-screen to be set by people creating the issues.

Without the (or even a) ranking field being used as the sort order, Jira has no way to know how to order your issues. Consider a backlog ordered by priority: * ABC-nnn - high priority * ABC-nnn - high priority * ABC-nnn - high priority * ABC-nnn - high priority * ABC-nnn - high priority * ABC-nnn - medium priority *…

You'll need to find an app that can record the amount of hours people have on their contracts and accumulate the work done on their requests to compare with what they have left. This is something that I've seen asked for a number of times, but I've never seen an App dedicated to it (I've implemented it with Apps I've…

Jira has a lot more power than Trello, and unless you have really really simple issues, it needs a bit more than "type a summary and move on". I'd get your admins to keep Jira issues as simple as possible (just keeping the summary mandatory) - that's as close to "one line at a time" that Trello does. Templates won't help…

Are the bugs workflow status mapped on the bugs board? What type of board is the bugs board? Are bugs a standard issue type or a subtask type?

There were some versions of Confluence where you could grant a write access (the way read restrictions work have never really changed) but it was causing so many problems with so many people (not to mention security bugs), Atlassian reverted to "you need edit rights at a space level, and restrictions can take that away on…

The only way to "restrict" people's access to issues in a project is via the issue level security These rely on the same things permissions do - roles, groups, individuals, user or group custom fields and dynamic roles (reporter, assignee etc) You will need to base your restrictions on the content of user-related fields,…