Comments
-
That's not the transition id, it's the status id.
-
That's correct, yes. You can't trigger transitions that are not valid for the issue, so the list isn't a lot of use, and it's best to ask the system what is valid, and parse it for the one you're looking for!
-
There isn't one. The question is quite difficult, because "a list of all transition ids" could easily look like 10010, 10020, 10020, 10020, 10020, 10022, 10024, 10030, 10034, 10035, 10035, 10035 and so-on. They are only unique within the workflow, AND they can be shared. Fetching a transition without the context of the…
-
You might want to have a read through https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions and, as Thomas says, concentrate on how you are using the "browse" permission.
-
Looks like your "scarce" background is a good solid one, you're absolutely spot-on.
-
I'm afraid there is nothing to "solve". An issue should only appear once on a board, so it's doing what it is supposed to do.
-
I suspect this is related to " https://answers.atlassian.com/questions/15292430 " and it's starting to make me think the question needs to be clarified - what do you think is missing here? What field are you looking for? If you go to edit a screen (as an admin), you are given a list of all fields in the system, so if you…
-
The JIRA data is quite complex and a lot of the relationships are logical. If you use the provided UI and external calls as designed, you can get sensible information out of it. Reading the database to do this is pretty much a joke, because you have to recreate all the logical relationships. You would be better off…
-
Um, the response was some questions, which you've not fed back with. I think that's why no-one else contributed - we didn't have enough info.
-
Hmm, ok, where did you see this suggestion that there's a problem wiht Jira/Tomcat and 11G? What are the symptoms (what does the log file say?) Are you using the right Oracle drivers? Have you raised this with Atlassian support? As Tomcat and 11G are supported for Jira, they should help you
-
A link is an indicator of a relationship between two issues for some reason - any reason you choose really. A duplicate, impacts the other one, one blocks the other, they're the same colour, anything. A link between two issues is mainly for user information, not a lot more. An Epic link means that the story belongs to a…
-
p.s. that's for Cloud. Server versions will still have it until 7.0 is released.
-
In other words, you can't. There is no wiki markup, it's gone.
-
It's aimed at a wide range of audiences. A lot of the corporate and government clients would simply not allow an external process the elevated rights required for setting up the database correctly, so why bother trying to code for something you mostly won't be allowed to do. You should be doing it in accordance with your…
-
I'm afraid that if a project has a scrum board, JIRA Agile will take you there rather than the project.
-
JIRA Administrate permissions do not automatically mean you get project permissions - you have to explicitly say "people in the admin group have project permissions". Project admins have always had the right to configure their own projects. I believe Cloud used to default it this way, but Atlassian are moving to a more…
-
I'm not sure what you've done now. You do not want resolution on the edit screen, because that will break your data. And I don't know why you need a validator either.All you needed was a transition screen with the resolution on it.
-
The "pop up" is the "transition screen".You absolutely do NOT want "touch Resolution and choose" because that means anyone going into edit the issue will break it.
-
Off the shelf, JIRA ships with a "resolve screen" which the default workflow uses as I've described above.If in doubt though, create your own new version of the screen and use that in your transitions. That way, you won't break anything unexpectedly, and you can use names that make it clear what you're doing.
-
Go to Admin -> Issues -> Resolutions, and make sure the list of resolutions contains all the entries you need Then, go into the workflow and look at each transition that goes from an "open" type status (e.g. open, in progress, reopened) into a "closed" type status (e.g. resolved, closed) and look at the "transition screen"…
-
Penny, does that mean http://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission is out of date?
-
Click "delete" in the options. That assumes you have the delete permission for the project. I strongly recommend NOT granting delete to most people because it really does mean it - the issue is deleted and to get it back, you're into restoring backups.
-
On the main menu, you have the menu "issues", use that to get to "search". There are two search interfaces, simple and advanced. The simple one has a handful of standard common fields you can search on, and for your case, just select the user from the field "assignee". In advanced search you can be more clever and do…
-
Ah. Try clicking the "Create support request" then.
-
It's not "our" product. It's Atlassian's *Service*. They also provide this "Answers" site for the community of their users to talk and help each other out.Your link goes to a Cloud JIRA installation that Atlassian hosts, but it's actually *your* system. If you cannot log into it, and can't use the "reset password" options…
-
No. Same state as before.
-
I think Jobin means that you will have to write a plugin to do that. I'm not aware of anything that lets non-admin users edit user properties.
-
Yes. Most of the JIRA jobs I got in the past started with "can you clean up the mess made by letting too many people have admin rights". It's still something we have beat into some clients as well.
-
It is easy - you have to get an existing admin to put you in the admin groups. There isn't really any other sane way to do it. Now, if you're on OnDemand/Cloud, then you should raise an issue with Cloud support at support.atlassian.com, and they should be able to get you added If you're on your own servers, see…
-
Map the incoming data to a temporary dummy user, then bulk unassigne them after import.