Comments
-
I don't know, I've not looked at the pricing recently.
-
Space tools -> Permissions -> Restricted pages tab will list all the restricted pages out, and let you remove them if necessary (Odd place for it, I instinctively look for it under "content tools", even after all this time)
-
Without scripting, no, there's no easy way to do this. You could do it manually with bulk-edit. Search for a list of issues where "Story Points" is 1, bulk edit the results so the new field contains 1 and blank out the old. Repeat for 2, 3, 4, etc.
-
You are correct, you will need to use SSO with Identity manager, provided by one of the other user directories.
-
It will probably work. But it will NOT be supported, so we can't recommend that you do it.
-
Yes. A licence key for Jira Software doesn't really care what version of Jira you are currently on (although if you're on a version below 4, you will need the key in a different format). Take your current numbers, buy the increase and apply the new licence.
-
@Omar Herrera- @Monique vdB and some of the other Atlassians (I'm not sure who else can do it!) can enable that for you.
-
It's confusing, and I think Atlassian have made a poor choice of words. Applications are the main products - Jira Core, Jira Service Desk, Confluence, Bitbucket etc Plugins is the original (and most sensible) name for "compiled chunks of code that you can add to one of the applications that change or extend…
-
You could get a third party to run server for you if the "unable" is for hardware/infrastructure reasons.
-
There's one migration issue - you can't do this at all. 7.6 is ahead of 7.2 and you can't downgrade Jira systems. You can upgrade from 7.2 to 7.6, and then use project import to pull in stuff from another 7.6
-
As mentioned already, admins can remove restrictions.
-
It doesn't "get" it from anywhere. Localhost always means "this machine I am on now". The port 8100 is set in your Tomcat server settings as the port the Tomcat will listen on.
-
You would not usually add acceptance criteria for a component - they're supposed to be parts of an overall project, not items that you complete, and the idea of a component having a status is nonsense. You should be doing both of those in issues. Description makes sense, but most people define components as clear obvious…
-
Jira's assignee field is a single user because of exactly that - multiple assignees invariably goes wrong (except in pair programming). I've yet to visit a place where multiple assignees has not gone wrong, one case only had three developers and it still went wrong.
-
Both are correct. You have a licence in your my.atlassian.com which is valid up until 27 Feb 2019. The licence on your server is an older one. You need to copy the licence from your my.atlassian.com account into Bitbucket - it doesn't know you have a new one.
-
That suggests the application you are adding the links to does not have the right protocols enabled to talk to the application at the other end of the link. This is usually the case when more recent applications have stopped using TLS1.1 and TLS1.2 because they are compromised and shouldn't be used any more, but other…
-
You need to get export add-ons, or pick gadgets that implement exports.
-
There are no "settings" for this, links are simple html links. To open in a new tab, use a right-click. There are some requests with Atlassian to enable links to be set like this, but they've rightly closed the ones for internal links as that's poor user experience. The one for opening links to other systems in a new tab…
-
It's the same answer as given before. Admin rights mean admin, not can do everything and bypass all the other privileges.
-
Could you try this in a different browser? I don't see that behaviour at all, which suggests you have something in the browser doing it.
-
Same answer
-
There is no way back on Cloud. Your best bet is to set up your own Server version and migrate (or get a server provider to host for you). We are all hoping the "new interface" never makes it to server, and we're pretty sure it won't any time soon (the noises I've heard are "no chance before the next US Summit and you're…
-
Yes. Ask them to use the work log
-
First, try modifying the notification scheme to say "when issue moved, notify reporter". Second, don't worry. When an issue is moved, anyone who goes to the old <jira>/browse/<project>-<sequence>, they are automatically redirected to the new one.
-
The ports are the same whatever flavour of Jira you install.
-
No, I'm asking you what you are trying to "turn off". A random collection of words that tells me nothing is not useful. Please answer the question properly.
-
Nope, wrong. Export to CSV is fully enabled in all all Server versions of Jira, and still available on the last Cloud system I looked at a couple of minutes ago. What are you looking at?
-
That's not really right, I'm afraid. Your problem is that a board is a view of issues, not a container. Adding status to the list of status is fine, but you needed to edit your workflows to use those status as well. Once you'd done that, your boards can use the status in columns. As for the workflow edits, you do not need…
-
Labels and good words in the title are the two main things.