Comments
-
I'm afraid "I cant remove the Default Screen from the Create Issue screen" does not make any sense - a screen is a screen, it doesn't contain other screens. To me, it looks like you have not got your screen-scheme correct. Your system is using the default screen for everything because you have not told it to use your new…
-
No, that would be the same as the done column.
-
There's not enough information to help you here. Have you checked that the plugin is installed (i.e. on the list of plugins and not greyed out as disabled)? What have you done to try to "access" it? How have you configured it? (If those all make sense and you think they're ok, then could you also have a look at the log)…
-
Ahh excellent. Sometimes a clean database is the most simple option.
-
Stop Jira, drop all the tables in the database, remove the contents of your Jira home directory (move rather than delete, just to be on the safe side) and restart Jira. If, however, it really is just the database, then I'd stop Jira, create a new database for it, then hack the dbconfig.xml file in jira home to point to the…
-
It's the same process in 3.5
-
Fields in Jira are either required or not. For the entire life-cycle of an issue. (This is a known weakness in Jira, but it's not obvious at first). You control that with field configurations. Screens are pretty much irrelevant here, all they do is say "show these fields to users if they're on this screen". The work-around…
-
Looks to me like you just have the attachment field on the create screen and the vault will do the rest.
-
What do you mean by "Document vault"?
-
Events are for telling other bits of the system that something has happened (e.g. "on event X, send email"). They do not change the issue in any way. (Although, you can set up listeners to do things to issues when events happen) Timothy has the right answer for what you actually need to do - use a post function to change…
-
It's well buried, but in the right place I think - the same place you'd instinctively get to when trying to delete or rename.
-
Go to the custom field list of options and disable B and C. Your users won't be able to add them, but they'll still appear in searches. (Note that this is only possible from JIRA 4.something upwards)
-
You'll need to find/write code to do it if you want it to be automated. Start by defining how you want to trigger the "transfer" and consider what you actually mean by "transfer" - is it a plain divergent copy? Or a sychronised copy? Or a complete move (where you'd delete it from the source system)? Or a partial move…
-
Yes, it's fine to use both.
-
That's not marketing, it's telling you that you've got an unlicenced plugin installed. Remove the Gliffy plugin from your Confluence installation (Admin -> Manage add-ons) or get a licence for it.
-
This is just blocks of log that I can't really read. Could you tidy it up and explain the problem?
-
The number of issues is shown on the issue navigator, and in several other places. Many of the gadgets will give you that result - try the "issue statistics" for example. For that one specifically, you choose a field to report on, so you could choose something simple like "project" and it'll give you the totals from your…
-
Ah, ok. The other thing to check if it's just linking - that is a specific permission in it's own right. So I'd check that the user has the right to browse and link the Epic (but still not edit!)
-
The reporter of an issue can only edit that issue, not the issues linked to it, unless they also have edit rights on the linked issues. The links are not important, permissions only apply to the current issue you are looking at. Check to see if the user can edit the Epic .
-
I'm sorry, but I don't understand the reasons you're jumping around or where the problem is. The answer I gave originally was clear, concise, and accurate. So I didn't understand why you were asking questions that implied you had not understood the original answer. Your follow-on questions were unclear and did not really…
-
Yes, I see that, you keep saying it. And I've told you the answer three times. Grant "reporter" the right to edit issues in the project. That's it. Simple. Job done. Only the reporter of any gven issue will be able to edit it. I don't understand why you start banging on about other users. You don't seem to be understanding…
-
I don't think you understand your requirement. Please think it through - who SHOULD be able to edit the issue? These are the people who you need put in the "edit" line in the permission scheme. If someone should NOT have edit rights, do NOT put them in the scheme.
-
That's not what you originally asked. But it's the same answer really - you let "reporter" and "role: developer" edit the issue.
-
Limit the "edit" permission to just "reporter"
-
Depends on how you are representing them in JIRA. If it's plain JIRA with no add-ons, then it could be quite hard, unless you've built something to do it. Or, if you're using test addons, then the answer is "maybe, but you need to tell us which one(s) you have"
-
You do not. JIRA uses the resolution field as an open/closed indicator. You can automate it completely, by setting/clearing it in post-functions in your workflows, but you can not just remove it. If you don't set it, the issue is open.
-
Stick Apache in front of it as a proxy (you can then drop iptables) and create a vhost to catch 8888 and 8090 access and automatically shove them to port 80 ?
-
I only know it because I did exactly the same several times when I was learning JIRA... :-)
-
Ah, I know this one. 10m is 10 minutes, not months. You can only do weeks, days, hours and minutes in the range searches. I think the closest you can get is by using the endOfMonth() functions, or something like > 30d and < 90d
-
If it helps, there's a 1:1 unique relationship between them - a step can only have one status, and that status can only be used by one step in a particular workflow. I think of steps as being the framework that you hang a workflow on to, which includes the visuals of what the users actually see (they don't really see steps…