Comments
-
There's no effective difference between those two access levels. The reason is that JIRA is now made up of a framework and applications. There are two applications at the moment - JIRA Software and JIRA Service Desk. JIRA Core is the framework. When you give someone a plain JIRA user licence, that gives them access to Core…
-
Please do not say "resolution status", it's confusing and misleading, because Resolution and Status are two separate things, and we can't tell which one you mean in the right context. Resolution is a field that tells us that an issue is "closed", and tells us why it's to be seen as closed. Status is an indicator of where…
-
I forgot, I should have said I'd prefer the "scripted field" route, but I have not tested it, and I am not 100% sure that the boards will be able to use that as an estimation statistic. That's why I mentioned the listener - because I know the boards will be able to use a numeric field.
-
You add the select-list with your numbers as normal, putting it on the create, edit and transition screens, but you do not add it to view. Then you need to choose between 1. Writing a numeric "scripted field" which will read the value from the select list, convert the label into a number and display that 2. Writing a…
-
No, with Confluence, it's user access, or anonymous. Anonymous spaces are visible to everyone.
-
I suspect you'll find the fields are of two different "types" and hence the code can't "cast" from one to the other.
-
No, you're going down the right path (although they're turning that add-on off in some places). The transition screen is an "edit", so a "message custom field (for edit)" will work here. The usual mistake people make here is to not put the message in the field's default value, they use the description!
-
That's a good start, but I think you need to go over the atlassian-plugin.xml and possibly add something to the pom.xml
-
No, it's a known annoyance. JIRA has several types of "view" for a field, and a field must tell it which views it supports. Obviously, there's a view view, but it's also got edit, xml, search and I think there are some others. Create, Edit and Transition screens all ask for the "Edit" template for a field. The read-only…
-
It's been a while since I tried it. I remember the way to go was to use the current SDK to create the plugin skeleton, and then only use the java code in it. The rest I had to work out for myself.
-
The code in that tutorial is mostly valid, but is out of date, it sort of stopped working with version 6. You have to change the pom.xml and other bits to update it to make it with later versions of JIRA
-
I do not understand the question. Tomcat is an application server. JIRA is an issue tracker. They do different things. (And JIRA runs on Tomcat)
-
Is it one specific file, or all file uploads? If it's one file, then the question is what's the difference between it and files that work. If it's all of them, it needs to go to https://support.atlassian.com because the next step is to start looking at logs, and only they can do that.
-
Admin rights are separate to the right to edit issues or move them through workflows. They're about configuring JIRA, not using it. At the top of the issue, click on the project name, to get to the project header view, it'll be displaying a board or some filters etc. At the bottom of the left-hand panel, click project…
-
JIRA has a "cascading select" field, but that's a simple "select one item to determine the options in the second half" For different types of field, showing and hiding fields and so-on, you need add-ons for field types that support that. Or you will want to take a look at ScriptRunner's Behaviours module, which enable you…
-
Not quite. It is something Atlassian are working on, but it is going to be a long path. Project admins can deal with users, versions and components, since a very early version of JIRA, and it's not changed since, until JIRA 7.3 took the first step and allows project admins to edit a workflow if the workflow is only used by…
-
Not really an Atlassian thing directly, as Java memory handling is fun! There's a good introduction to most of it at https://smarttechie.org/2016/08/15/understanding-the-java-memory-model-and-the-garbage-collection/ (diagrams aren't great, but the wording explains a lot)
-
You need to be an administrator to be able to edit a workflow. Status is not a field, and can't be "edited", you have to move the issue through workflow transitions to change it.
-
Yep. My guess is because it's the least used of the four they support. But that doesn't really explain what's taking so long, just one reason that feeds into it.
-
They'll need to build their own filters, and not rely on JIRA's reporting functionality. I find it easier to just get it right, even if I set the resolution for them as part of the workflow and hide as much as possible, so that the data is correct. Although there's a short essay on why resolution really should have been…
-
Generally, yes, but not always. Have a look for all the AO tables in there. You should find loads, with formats AO_<number>_<name>. (The number is based on your add-on key, so it's unique and groups related tables together)
-
It's in the active objects tables.
-
There's no official promised date yet. Might want to follow https://jira.atlassian.com/browse/JRASERVER-44734
-
JIRA only uses one database at a time, (unless you add code that explicitly reads another) so yes, your data is being stored in the Oracle database, if that's where the JIRA database is. Generally, you should not worry about the database, you should not be accessing it directly.
-
An issue is open when it has no resolution. It's closed when it has one. That's how it is defined in JIRA and you need to set a resolution to tell the system the issue is resolved.
-
This is something that needs to go to the add-on vendor. You say you can't create an account in their JIRA, but there is a support portal at https://lab.spectrumgroupe.fr/confluence/display/SBD/Support
-
Are you sure that your developers have "admin" - log in as a developer and check how many options they have under the admin cog - does it have a list of several options like "issues, add-ons, system, etc" or is it just "projects" If anyone other than those two users have admin rights, then your system is completely broken…
-
Ok, great, so now, look at who is in all three of those groups - Administrator, jira-administrators and site-admins
-
I'm not aware of anything on the Atlassian side that does any integration, so it may be worth checking the docs for opmanager to see if it has anything. If not, then I'd be looking at getting opmanager to simply push data into JIRA over the REST interface when events occur.
-
First, define what you want from "integrate". You'll then need to find or write something that can do it. I'd start by searching the Atlassian marketplace for any connectors, then maybe head to PractiTest's site to ask what they have.