Comments
-
You'll need to define a useful KPI (or set thereof) and then monitor it to see if it meets them. Latest version of Server has an extended range of JMX functions you might find useful.
-
Jira does not have that functionality. You'll need to explain which testing add-on you have.
-
Jira doesn't really do test case management, but there are a number of options on the marketplace that add them. See https://marketplace.atlassian.com/search?product=jira&query=test%20management Note that I work for one of the vendors (albeit in a different area than our Test tool), so I'd be biased if I recommended any…
-
Ask for help over at https://support.atlassian.com/contact
-
You're missing the point - your code is trying to use a separator that is invalid. You simply don't need to try to set it, just pass the number into the field.
-
Install a Jira that was released before the end date on your licence. You'll then be able to paste the licence key in during installation.
-
Give them a chance, 6.7 only came out this week. I'm quite fond of the add-ons Niklas mentioned, if you do have some money, they're both very good.
-
Code. The user directory is not a pluggable thing, you will need add-ons to create these extra fields and store them. It also depends very heavily on what user directory you are using - LDAP, internal crowd, external crowd, etc all very different things.
-
You cannot put formatting into a numeric field. The field accepts whatever you have for a decimal point and stores it as a number, not a string. It is your language settings that determine what you see when Jira renders a number.
-
You'll need some code to do that. ScriptRunner or Automation can probably do most, if not all of this. But you would not do it as a validator, it's a post-function or listener. A validator checks things are ok before letting things happen, they should not alter data (This is Jira-speak - validator is an important word here)
-
I'm a bit lost - the dropdown in the scheme should list all workflows, irrespective of active or not.
-
The built-in "cascading select" field will do two layers, but for the three you describe, you either need separate fields and something like ScriptRunner's Behaviours to tie them together, or the multi-level cascading select add-on from the marketplace.
-
Could you explain "fails"? It doesn't start to give us any information about what is wrong.
-
First hit on my search engines is right - https://confluence.atlassian.com/kb/single-sign-on-integration-with-the-atlassian-stack-794495126.html
-
But you said you don't have a project role Reporter (and I would strongly recommend not having one either, as it will make things even messier. If you want a role to explicitly control creating issues, call it "creators" or something similar. "Lower on the list" means when you click "add permission" and select one or more,…
-
This is correct. Your filter explicitly excludes issues from P1. By definition, issues in P1 cannot have component C1, so your filter won't ever get anything from it. If you want to see issues from P1, include them in your filter. Try ( project = P1 ) or ( project = p2 and component = C1 )
-
No, that would be a quick-filter and appear under the quick-filters drop-down.
-
Ah, hang on, there is confusing language in the documentation here. There are "project roles" which most of us call "roles", and "roles" which are *dynamic* but most of us don't call them roles because they are fields. These "dynamic roles" only appear as functions in certain places. Such as permissions. For your case,…
-
JQL has issue in linkedIssues('ABC-123')
-
I'm sorry, I don't get why "I don't want people to contribute in our collaboration tool" is useful. The worst case is someone adds a page in the wrong place. Move it to the right place. With your approach, people will start creating pages in the wrong place, and you won't know anything about it until you realise it's a…
-
I am not sure what you are asking, so two answers: If you are asking about the issues going through the workflow, then the changes are all recorded on the issue's history If you are asking about the administrators making changes to the workflow, then no history of that is kept unless they choose to keep copies of each…
-
Makes perfect sense to me. Why should I not be able to create pages beneath other pages I can't edit?
-
This sounds wrong to me. A centralised single Confluence alongside a similar Jira gives you benefits over having several. The only advantage to using several Confluences is it's easier to look after access if you have stuff to hide, and you don't have to worry about users discovering each other's accounts (If, for example,…
-
The admin right you use to create a project says nothing about your access to that project. You need an admin to check the permission scheme on the project.
-
That's a standard ftp problem - the ftp user doesn't have permissions to see the Jira directories. Either use an ftp user who does, or open the permissions (I recommend the first)
-
No, because they have "create page" rights in the space. The only way to stop them adding pages beneath other pages would be to remove their "view" rights to the parent pages, so they cannot be on the page to create the child page.
-
Get an admin to put you in a role or group that has Administration rights in the permission scheme for the project.
-
Use the backup option to get an xml export of the source system. Use the restore option in the new one to import everything.
-
You should check the mail server log to see why it is rejecting you, and maybe get more data in the Jira logs by following the troubleshooting doc above.
-
The easy option is to get an add-on. They've done the coding for you.