Comments
-
Confluence has a neat trick where you highlight a line or block of text and a little box appears above it. The box contains the icon for "in line comment", but if you have an application link to your Jira, also a Jira icon which gives you a "create issues from text" function. I think that's what Scott is using (It is what…
-
Start with a look at your logs: <jira home>/logs/atlassian-jira.log will usually contain a reason for a crash. It's the application log, so it will show application level faults. If that just stops dead, then <jira install>/log/catalina.out is the next place to look (this should contain a more system level error). If both…
-
The key is not the same type of field as whatever you are trying to copy it to, so the field copy function fails. JSU can't convert between the types, you are going to need something a bit more clever.
-
Mmm. Can you have a look at three more things? All long-shots, but need to be checked. * What status is the issue in? And what is the status category of this status? * Could you re-index the project and see if that changes anything. * Could you check that the Story Points field there is a simple numeric field type?
-
No, I think you've mixed up a lot of old documentation or misread some guides. Atlassian don't have a product they call SAAS, but Cloud could easily described as such a system. Server and Data Centre are different products (DC is Server+), related to, but not the same as Cloud. In short, sign up for Cloud if you want a…
-
Ok, good. If that says story points are selected, then the issues in the backlog do not have story points set. Could you select one that is on the backlog with a grey circle and look at it in the full issue view?
-
Unmapped status will be in the unmapped column on the column definition screen. If you have no unmapped status, then your workflow is already fully mapped, and you'll either want to move status from existing columns, or edit the workflow so you can add more of them to it.
-
Scrum should have them, and when I create Scrum projects, they're there.
-
Go to board configuration, look for the columns tab, and click "add". You will then want to add one or more status into the column to make it active.
-
Should be Labels = equipment and labels = improvement Is that what you've tried?
-
It's in your second screenshot
-
Sorry, I should have said "estimation statistic" as the full name of the field in your screenshot.
-
Not really. Jira tends to be permissive, rather than restrictive, so the approach is "grant permission to those who should have it, and don't give it to those who should not". There are some tricks you can play with workflow properties, but they're a bit messy compared with a permissions review.
-
It should be in the second picture you posted - the estimation field for the board (not the time tracking bit, just estimation). It would not be the first time I've run into Jira systems with more than one "story points" field, and the wrong one is selected!
-
Could the "estimation statistic" be looking at the wrong field?
-
They're working fine for me.
-
Depends on the admin and your processes. If they're enforcing a standardised way of working, you'll need to come up with a good reason to change that. If they're not doing it for other reasons, you'll need to ask why.
-
Custom fields contain custom field data (I don't know if you used a string based custom field, or a select list, which will contain options). The security level field contains a security level. Copying a value won't work, as they're different things. You will need to do some scripting - something to read the string/option,…
-
I'm afraid it's not a simple minor change to a file. You'll need to rewrite a whole load of stuff in it, and check all the add-ons AO data as well. Miss one thing, and you won't be able to import, and will have to re-evaluate. I would strongly recommend upgrading, as per docs.
-
You would have to ask them, we're end-users like yourself, we don't know them any better than you do.
-
It's not possible. There is no "edit status", you MUST have a transition to take an issue from one status to another. To implement a new button that uses ScriptRunner to do this, you are still going to have to have a transition there. Your description feels like you are massively over-engineering this. A normal transition…
-
It's by design. Someone has put the "do not edit" flag on closed issues, so you can't edit them.
-
That's why I was asking about the field. You need to put something into it, which means editing the issue. My guess was that you have no data for them, as the grey circles contain nothing.
-
Pick one of your stories, and go into it (the main issue view). Click edit, then look to the top right for "configure fields". Use the "where's my field" option to uncover where it's not been set up.
-
Sorry, I meant transitions out of the current status? Are there others? If so, are they showing?
-
Forget the SQL, it's slow, complex, painful and not needed for what you're trying to do. issue.getSummary returns the summary. Try issue.getKey() and issue.getDueDate for the others.
-
Are there any other transitions showing at all?
-
Also, if you have Jira Software, then an administrator can "simplify" a workflow, and that lets the board owner maintain it.
-
No, Jira Software only supports one Epic type.
-
Cost - DC is relatively expensive and you'll want more kit to run it on, which is a bit more complex to set up. (No point going to DC if you've only got one node)