Comments
-
There's two questions here, sort of. One is about scheduling, and the other about follow-ups. On the scheduling, it's pretty much a "no". It would seem only a small fraction of Atlassian's users want this, so although they've not closed the requests to do it, they don't seem to be high on the list. There are also…
-
No, I'm sorry, I'm not explaining this very well. You need to look at the permission scheme. That controls what you can do, but not by "having the same permissions", it's by a set of roles in the permission scheme. Permissions don't usually get given to users directly (it is an option, but one most people avoid). The…
-
Permissions are the only thing that control the items on that list. It doesn't matter that you only have one scheme, what matters is what it says - do you match the rule that says "can log work" for example?
-
The options on the list are mostly controlled by the project permissions. If you want to log work on an issue for example, you have to have "work log" permission. Check the permission scheme for the project(s)
-
I don't think this is counter-intuitive at all. When you have nothing in the page restrictions, then the page is not restricted. When you restrict the page to only Joe, then only Joe can see it. When you remove that restriction, the page goes back to being unrestricted.From your question, I suspect that you're not quite…
-
You could be using the word "edit" to mean two things here, so I'll answer both. If "edit the status" means "change the status to another one", then you are talking about a transition in the workflow. You should place conditions on the transitions you want to protect. A simple example is just to say "only the reporter can…
-
No. The creation date of an issue is when it was created in JIRA. That's the data it was intended to capture, so there's no way to amend it, because you shouldn't. If you need a "date issue actually happened which is not necessarily the date it went into JIRA", then create a custom field for that instead (and default it's…
-
Editing workflows is covered at https://confluence.atlassian.com/display/JIRA/Configuring+Workflow
-
Click on them
-
Step back - you've given us a list of transitions. The number in brackets is simply the unique id of the transition in the workflow definition, it doesn't really matter too much. What you need to do next is descend into the transitions and look at the "conditions" on them.
-
Click "steps" on the workflow you think is a problem, you'll get a text representation of it and you can then descend into the transitions to check their conditions.
-
No, you don't need to change anything - you just need the right to edit workflows - then you can look at them in the list of workflows. You don't need to look at schemes (other than to work out what workflows apply to a project/issue)
-
You need to be an admin and able to edit the workflows, so you can look at the full details.
-
Both. You need to read the workflow conditions, probably in conjunction with the permission scheme. Start with the workflow though.
-
There's no picture of your results (this seems to happen to Answers a lot when trying to attach stuff, you're not alone...) You need to have another look at both permissions AND your workflow. Permissions schemes are better thought of as a list of flags that don't really do anything about actions themselves. All actions in…
-
Sorry, they may come across as quite grumpy, and I do not really mean to sound like that. My point is that it's well worth asking what they're looking for directly - it might save both you and them a LOT of time :-) On a more positive note, the last time I had auditors ask for something like that, I went straight back with…
-
Then they're wasting your time, and their own. Jira is searchable, auditable and can tell them a lot more than 30k plain text records. Are they really going to pay someone to read all of that? I very much doubt it, they are almost certainly going to either search it, import it into something to help them with their audit,…
-
The CLI is limited by the same limits that exist within Jira. You can override this internal limit - see https://answers.atlassian.com/questions/64517/jira-export-50000-issues-to-excel?page=1#64520 for how, but bear in mind that it's going to kill performance while running, and unless you've got some decent hardware,…
-
I'd grab it with xml and whack it through an xslt transform.
-
Run a filter that includes the ones you want to move. Use "bulk edit" from the tools menu (you may need check that this is available to you via "admin -> global permissions"). Select "move" and it'll ask you what project to move them to.
-
You've given it the wrong email address, or your mail system isn't delivering it (misconfigured, or seeing it as spam), or your mail client is filtering it into another folder (rules or again, spam) There's not a lot you can do about this - you need to fix your email system or look at the email you actually gave to your…
-
Yes, you can export the Cloud site and import it to another Cloud site or your own server.
-
Apache Axis is not essential for writing java to talk to Jira. Have you tried the examples under https://confluence.atlassian.com/display/JIRA042/Creating+a+SOAP+Client ? If you've got that far and want to use Axis to help build up your application, then you may be better off asking in Axis related forums/communities,…
-
It does what it says - when the 3rd line runs, it fires an event. Events are, well, um, "events" that other bits of code can pick up. It's a bit like having your issue jump up and down yelling "something just happened" to the rest of Jira. By default, the only listener really built in to JIRA is the one that sends emails…
-
No. There are plugins around that do it, but I don't think any of them are in the list of plugins installed in OnDemand, so you can't get them. In the longer run, if OnDemand does include one, you can install your own plugins, or you go to your own install, there are two variations - "show last comment" and "show all…
-
Totally off-topic, but yes, click delete.
-
Ah, that makes more sense.Problem is that the CSV importer can not change the parent issue of a subtask.
-
This sounds like it is wrong, and I think you need to re-explain the problem more clearly You say > Before: A sub-task SAM-1 has a parent story PAR-1 No. No it does not. SAM-1 cannot possibly have a parent story of PAR-1. Subtasks belong to the same project as their parent and are always higher numbered. So SAM-2 could be…
-
Yes. But you need to define what you mean by "integrated". It's a good word to give us a generic idea that you want two systems to talk to each other, but without the detail of what you want to achieve, you can't get an answer any more detailed than "yes"
-
Not if you want to interpret it in your program. If you look at the UI though, you'll be able to work it out, and it's very rare that Atlassian change the "type" of field (I think the last one was the conversion to allow many components to be selected instead of one, and that was in JIRA 2 or 3.0) Broadly though, you'll…