Comments
-
Ouch, there's no need to shout. If you want anything resembling an answer, you need to tell us what Atlassian product you're using. And read Andy's comment - your posting is rambling and unclear.
-
You can use "issue security" to do this, creating a scheme that says "reporter" and then defaults, but that allows users to remove the security and it's a bit fiddly. The better option is to do what Atlassian do in their support projects and use "current reporter browse" instead of just "reporter browse". This is disabled…
-
Ok, what you probably want to do is copy your existing workflow, change the new one so it does what you need, put it into a "workflow scheme" and then change your project so that it uses the new scheme. The link I gave earlier is well worth a read on this subject, it's better written than anything I've posted!
-
Excellent, that's a really good explanation of what you've done and it helps me match the words I'm using to what you're saying. There's certainly no need to apologise for the wording, all of us are probably guilty of uncertain translations, and I know I use bad words a lot. I think there's two parts to the question here,…
-
That's actually useful information in explaining your setup :-) The question of setup is about what you've done to customise Jira. The main question ihere is probably around what workflow you are using, but if you've "created a project and started specifying test cases", then it's quite likely that you are using the…
-
You've not explained how all of this is set up. It sounds like you simply need to amend your workflow to allow the status changes you want to work with. But we don't know what you've got now...
-
Posting on a 3 year old thread often doesn't do much as things have often moved on.But the *generic* answers here are still valid - you are going to need to establish the pattern of when it occurs and read the logs to see what errors you might be getting.
-
Good to rule the email out. Cloning doesn't take comments, it's only the issue data it copies, so you could still have the comment problem. Having said that, it's unlikely, because I've seen issues with a few hundred comments working fine, it's only when you get into silly numbers that problem occurs, and humans generally…
-
atlassian-jira.log is the application log you want. The question about fields is a bit of a guess, because I've seen custom fields that cause this error when they try to render the issue view (my code was awful!) Another thought though - I've also seen this happen when there's a huge number of comments on an issue - could…
-
Not sure, those errors are more likely to be gadget or report errors, possibly caused by the same issues, but not the root cause of the problem. Catalina.out is a good place to look, but I'd also check the application log (rather than random guesswork starting from "it's usually, but not always, jira-application.log"), go…
-
What is "special" about these issues? What is different between them and the ones that work? What does your Jira application log say?
-
Sorry it wasn't particularly positive. I do think the relationships between parent and childen could be improved, but I can't think of a decent suggestion on how to improve it in a generic way that will help a lot of Jira users. The best I've done without having to do any code myself is to use the Jira Toolkit to display…
-
Jira's issues are all separate entities really. Subtasking is a special link which allows the time tracking on subtasks to roll up to the parent and shows the relationship between child/parent issues, but it does nothing more than that. So, no. You'll need some coding to handle that.
-
We follow much the same pattern as Bob. We backup overnight, every night, but don't take it offline.
-
There's quite a few questions here, and my knowledge isn't quite deep enough to be able to point you at all the things I think you need to look at here. I would strongly recommend contacting Adaptavist support about this - the Bubbles Forum addon has gone through a lot of changes, and has effectively been retired in favour…
-
Same basic question as asked at https://answers.atlassian.com/questions/11460880
-
Right, so it would have saved us a LOT of time if you had said "this is an OnDemand instance". (I have no idea what your middle paragraph has to do with it, your VMs are irrelevant to OnDemand) You need to raise this with OnDemand support.
-
In the data directory you chose on install
-
What does your log file say?
-
I'd like to see "version and component" management as a separate permission to "project admin" myself, but it's not been done yet. On the other hand, I've seen what happens when you let developers set their own versions, and it quite often *really* needs to be out of their hands...
-
Your developers should be administrators in their development systems. They probably should be administrators in your test system if that's necessary, but the flavours of testing and how you do testing might do determines that. No. Greenhopper users are ordinary users. Generally, scrum masters would have project admin…
-
See http://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions for most of what you need to know about permissions (for this question, it covers versions) For adding gadgets, no, only administrators can do that. See http://confluence.atlassian.com/display/JIRA/Adding+a+Gadget+to+the+Directory
-
LMGTFY - https://confluence.atlassian.com/adminjiraserver072/upgrading-jira-applications-828787633.html
-
Ouch. You can't really. Deleted in Jira really does mean deleted. OnDemand has backups, but these are more for emergencies than looking for the odd mistaken delete. You could try a support call with them, but I don't know that they'll be able to help. (Also, consider severely restricting delete rights in the future. To…
-
Sorry, yes, I was generalising. Create a new workflow for "hotfix" only
-
Well, the short answer is that you don't. A transition only has one end-point, by definition. What you can do: Have many transitions that have conditions on them. For example, if you need to bypass all the QA stuff sometimes, have a transition from code review directly to staging. Add conditions like "only the project lead…
-
Why does there need to be a constraint? If an issue has a link to another that says "the issue at the end of this link might tell you something interesting about the current issue", there's no constraint, it's a relationship, shown by a link. If you need to impose constraints, that's a function of your business logic, not…
-
* There's a chunk of history we could try to explain here that would show you how we got to this quite inconsistent view, and a further conversation about why it's a bit broken in JIRA and why it can't be easily fixed, but I'll skip that for now because it's not that interesting. The simple response is that you should be…
-
Nothing. You don't really "add a project to a scheme". Schemes are groups of settings that you apply to a project. They don't change just because you use them on a project, they tell the project how to behave. Your reporting in the pie chart is simply listing what you have in the field. If you're using the scheme for a new…
-
I'm not sure I understand the requirement here, but it's pretty straightforward to set the status with groovy. You use it to execute the transitions required to get you into the correct status. I've got https://jamieechlin.atlassian.net/wiki/display/GRV/Services bookmarked for the basic code for pushing an issue through a…