Comments
-
>Disclaimer: Don't blame me for this; I didn't do it. I know
-
Ah, you mean the associative link table? I was thinking more of the business logic, not quite how they're stored.
-
To answer the question in the title too, "none". Components and versions are unrelated in any technical way. They have things in common - they go onto issues, they're configured by project admins at a project level, but no real relationship. As Volodymyr says, it must be the add-on - it sounds like it is intercepting…
-
The documentation does cover it, but it might not be clear that some fields have one extra control - Reporter, Assignee, Fix Version, due date and security level can only be amended by people who have the permissions to do it. You still need to put them on the screens, but they will be hidden by permissions if necessary…
-
It's not that obvious, I'd agree, as a lot of people here run into it when they're new to Jira. It IS logical, for two reasons. First, in most cases, "resolved" DOES mean "resolved". Secondly, if that's not working for you, it's not that hard to change it - remove the "resolve issue" screen from transitions into "resolved"…
-
Bother, I had a bookmark pointing to a doc on this for v3, but it's gone. I don't know if there's an equivalent page for v5.
-
Do you mean add it to a screen with all the other custom fields, or you mean you want to include it in the system field panels? Actually, I'm pretty sure you mean the second, which means hacking some code I'm afraid.
-
It's never intended to - resolved issues are "done" as far as Jira is concerned. If that's not how you're using resolution, then forget the "assigned to me" gadget, define a filter that returns what you need and then use the "filter results" gadget instead.
-
I still think it's the resolution.
-
I don't think you've missed anything on the status side, but I suspect you'll find that they are "resolved" (i.e. they have a resolution of some sort) and the gadget won't show those.
-
Ah, yes, I do. But I can't replicate it, it's working for me.
-
Nope, works fine for me. I still think you're looking at something different to me, I'm just following the doc.
-
That's not true, but I suspect that you're actually looking at something different.
-
It's the id of the value in the database. Go to admin -> priorities and hover your cursor over the edit links, you should see urls with id=x in them. E.g. Blocker = 1, Medium = 3, Dropped = 10024. That's the number it needs.
-
You can't do it - there's no built-in function for "set version"
-
It can take a while, yes. Think I've waited up to an hour before the backup contains everything.
-
Go to Admin -> System -> Backup and grab the xml from there.
-
You're very close already. Answers is running on Confluence with the Confluence Questions addon. If you download and try Confluence Questions, you'll find some differences (Answers is slightly tweaked to make it more of a public forum), but it is very similar
-
Oh, I see, you want a task that never gets resolved/closed. Change the workflow so that it doesn't allow anyone to close it (or even remove the "closed" status you don't need)
-
I'm not sure where the problem is or quite what you are doing. Do you mean you've got a task (lunch) with many programmers who might work on it? Are they using "log work" on it? Is the requirement maybe "we can not close the issue until the work logged has met the estimate"?
-
I'm afraid I don't understand the question. "Perminte pending" does not mean much. "Pending" usually implies some sort of holding state - for example "pending authorisation", "pending payment" and so-on. The issue cannot move on until something is done. If I have understood correctly, you are asking if you can create a…
-
Oh. Well, I think you're stuck then. You can't upload the required addons to do this sort of thing.
-
I'm assuming you mean Jira here? Jira notifications are handled at a project level, not issue. Whilst they contain issue data, the decision on who to send email to and when does not consider the data on the issue. So, you'll need to find/write something that will do this outside the normal notification scheme. A…
-
There's all sorts of things Atlassian (and the rest of us) might ask for, but the logs are very much the most important thing - they tell us what the problem is, or, failing that, they tell us where to look next. Best bet for Atlassian, use the support tools to raise a support request - it will bundle up the logs and a…
-
I'm afraid you can't. JIRA hides empty fields on the issue view to avoid (even more) clutter on screen. To change it, you have to hack JIRA's core code.
-
We can't do the work for you - you need to set up your server to connect to your gmail accounts. What documentation are you following, if any? And what have you done to try to configure it so far?
-
It's not clear to me whether you are looking at the workflow or the workflow *scheme*. You can't link workflows directly to issue types or projects, you have to go through a scheme. What you are doing is a three step process: 1. Define a new workflow 2. Define a workflow *scheme* that says something like "use workflow 1…
-
Er, you said you already had that.
-
Ah, gmail needs a bit of fiddling - https://confluence.atlassian.com/jira062/using-gmail-as-a-jira-mail-server-588582074.html
-
You need to follow the docs - go to mail servers and add a SMTP server with the right settings. You haven't told us what you're doing, what error messages you're getting or even what doc you haven't followed.