Comments
-
You will need to contact your JIRA administrators. We're end users of the software Atlassian produces. We have less access to your systems than you do.
-
Remember that only applies to Confluence 5.3 and above.
-
Odd, I've had no problem working with the attachments in the file. Could you explain what you are getting and why you can't open them?
-
The xml export is the way to do this. Even if zip were offered, it would just be a zip of the xml. You might want to explain what you mean by "xml did not do the job" - I've used it several times for creating test systems, moving servers etc
-
There are good reasons for other numbers to be used sometimes, so I was fishing for a reason really. But, exactly as you say - if you can keep it simple, that's good
-
What's wrong with keeping it simple and using the JIRA issue key?
-
No, that's why I immediately said you need an add-on.
-
OK. I translated correctly So my answer is right - you can't do this. You could try the "Field Security" add-on from Quisapps, which does do it.
-
I am not sure of my translation, but I think you are asking if you can hide fields from people? If so, the short answer is "no". JIRA does not have field level security. If you can see an issue, you can see all the data on it.
-
I have workflows that don't include "closed". You're absolutely right that "Strikethrough when there is still work to be done on it is confusing and putting something in the "resolution" field should only be valid if the issue is resolved". That's why you should not set the resolution until it really is done.
-
Yep, that's why you need to make sure your resolution is handled correctly in the workflows.
-
Then you have a hacked copy of JIRA where someone has changed code to deliberately remove the strikeout
-
They should be struck out because the resolution is set to something.
-
Er, that has nothing to do with this question - may I suggest you delete it and re-do it as a question, so that it gets an audience other than the handful watching this thread. And perhaps include links and references?
-
The resolution field is controlled by presence on screens, not permissions. So you need to check the create issue screen again. Also, look at the post-functions on the create-issue, in case you've got a resolution set there.
-
I think it might still be the edit screen. Screens are well buried in Jira, there's layers of config for them, but to make sure you are looking at the right one...- (you will need to be an admin on the project and a Jira admin to do this)- Go to an issue which has a resolution strikeout- Go up to the project it belongs to…
-
It's not the resolved-date, that's completely irrelevant. The resolved date is just "date someone changed the resolution from <empty> to <something> The cause is simple - you've got resolution on the create/edit screen for Defects, so your users are inadvertently setting a resolution. If that is the case, remove the field…
-
Nope, that's why I answered the way I did. The whole of JIRA is coded to assume that "resolution is set means the issue is resolved", you'd pretty much have to rewrite half the system.
-
You don't. An issue is struck out when it has a value set in the field "resolution". It has nothing to do with status. For your case, where you want the resolved status, but don't want the issue to show as resolved, then you need to * Change the workflow screen in use for transitions INTO resolved so that they use a screen…
-
It helps if you ask a useful question.
-
Ok, create a listener that listens for the "create" event, or use a post-function that can trigger it - both should have code that says "if rating == excellent, issue the close tranition" The easiest way to do this is probably to use "fast track transition" which you can find in the "Script Runner" addon. See…
-
Set up your workflow to allow the closing. Then, use a listener to listen for whatever change it is you want to trigger the close. (I can't tell you much more than that, it's not clear exactly what your trigger is here)
-
User macros are a feature of Confluence, not JIRA. What are you trying to achieve here?
-
Atlassian's answer is probably to add Portfolio to your JIRA, and use that in conjunction with Confluence.
-
All I know about doing it on IIS is that "Application request routing" does much the same as "proxy pass". I have done it, but it was many years ago, and I was able to muddle through the docs with some help from an IIS person. You have IIS running on your DMZ server, and when a user lads on certain urls, it goes and asks…
-
If you were using Apache, it's a straightforward "proxy pass" on the DMZ Apache server. I believe you can mimic this (although it's not pretty) using "Application Request Routing" in IIS. However, whatever method you use to do this, you MUST remember that Jira only has one base URL - it won't run properly if you use…
-
I usually create a board from a project, and then just edit the filter for the board. Change it from "project = x" to "project in (x, y, z)"
-
The Angry Nerds team is handled by groups.I think the point of a board is that they are team artefacts, I tell a lot of people that they should organise projects along assorted lines, depending on their data, processes and structures, but everyone gets the same advice about boards - they're for teams.Yes, there's…
-
JIRA Agile does not implement any "team" functions in this sense. You can either put them in groups for each team (and add the groups to the projects), or add them individually to projects. Once you've got users in projects, you include those in boards.
-
What, exactly is the field you're checking? The type and values you're looking for?