Comments
-
What does the documentation say you need to do for this? Pasting us a screen from another system with random highlights and no explanation is a usually very poor question and does not explain what your question is, and your text just repeating the title with no further explanation is equally poor. To take a stab at the…
-
No, the only difference you'll notice is that administrators will get the odd warning box telling you that it's unlicenced and unsupported. All the functions you have now will continue to work exactly as they do now.
-
No, Cloud uses Atlassian accounts, Google accounts or Atlassian-Access to provide users.
-
You will need to read the application log for the full error. It will contain the error you've seen on screen here, so if you open the log in an editor and search for the first line ("the end instant must be greater"...) that should take you to where you need to start reading - look at the block immediately before in case…
-
Jira doesn't have "tags" natively. How have you added them and why are they different to labels?
-
My guess is that your bugs are sub-tasks under stories? Sub-task estimates do not count towards velocity, as the estimates and commitment is done at the story level.
-
It's a necessary design - the user system is often external, so tehre's no way to control when someone exceeds the licence other than by blocking access at some level. The failure here is that it wasn't telling you that clearly enough (there should have been a warning message in the UI)
-
There are no SLAs in Jira Core or Software, but you don't need a 3rd party - the Service Desk application is Atlassian.
-
You can only do ranking with fields that support ranking. Numeric custom fields do not support ranking.
-
We can't help you with that - it's a system we know less about than you do! Best I can do is suggest you ask colleagues, team members, and the person who added you to the system or requested your access.
-
The url used in email is determined by the base-url of your system. It sounds like that is currently set to http://<yourjira> - change it to https://<yourjira> to fix it.
-
How are you presenting Jira through the host? You've shown us the settings for a "redirect", but this is not telling a service to present Jira on a url, it's just saying "if you land here, go there". Where are you actually running Jira and how is the proxy being set up?
-
You cannot do that because it is pointless. Sharing a dashboard is only useful for telling Jira which humans can see a dashboard. Your users are not components. What do you think the system would do if you shared a dashboard with a component?
-
We cannot begin to answer that until we know how your tests are being represented in Jira. We need to know how you have configured your native Jira to do it, or which Test Management App you have.
-
There's nothing I can find in the marketplace. I'm afraid you will need to build something for yourself.
-
It's working fine for me, I think we need to know what's different between your install and Tyler's.
-
Yes, you will lose anything entered between the backup you took and the point at which you chose to roll everything back. But you should have everything you had when you took the backup.
-
Correct, ~ is a fuzzy search for text.
-
That sounds correct to me. You said he only has watch in space_01 (the "edit only one page" suggests you've added him to the restriction, but that's irrelevant as he has no create/edit in the space). So when he creates a page, Confluence has to create it somewhere that he does have create access - space_02.
-
What are you pasting into Crowd, and from where? (Not the actual content, but where you're getting it from - a screenshot would be great, but blur out a good chunk of the key)
-
Correct. There's no geographically remote clustering yet (Data Centre itself was a massive challenge). It is high on the list of things to get into DC, but not ready yet. Some of our distributed clients have had significant success with simple network provisioning and tuning, but many reach for shared projects - separate…
-
You have a field called "account", which is flagged as mandatory for this project and issue type. So when you create an issue, you need to fill it in. But I'd guess you have removed it fro the create screen, so users cannot do that. Either make the field optional in the field configuration, or add it back to the issue…
-
No, it's not possible yet. See https://confluence.atlassian.com/confeval/other-atlassian-evaluator-resources/can-i-restrict-by-ip-in-atlassian-cloud
-
What do you mean by "customer key"?
-
I'm afraid voting is not going to help you with this. A vote is nothing more than a person putting their name on an issue (in the background, so you don't know who they are) to say they voted on it. The functionality is by person and is just represented as a simple count and to completely break your usage, Jira doesn't…
-
Projects and portals are different things held in different places, that's the technical reason the ids are different. All portals belong to a project, but not all projects have portals. Your code needs to understand when it is looking at a project and when it's looking at a portal and be aware that they are different…
-
Summary is a mandatory field because the system uses it *everywhere* for the human short description of the issues. If you took screenshots of the screens that your users use the most and redacted the summary, you'd quickly see that the system becomes virtually useless as a tracker, because you have no idea what anything…
-
Try setting the domain to point to your Jira server - no trying to redirect ports or services. Make it so jira.davidcubesvk.com points directly to your Jira server, and then try jira.davidcustsvk.com:8081
-
What type of board is it that is missing the search?
-
What do you mean by "access"? What is the php page on server 1 expecting to do with Confluence?