Comments
-
Could you list exactly what the "browse" line in the permission scheme for the project says? (Text is fine, just include the whole line of the table)
-
That's why we save and share standard filters. If you look at the dashboard gadgets (we set up shared common dashboards too), you can do things like "show this filter and push it through a report where the user can choose which field to group the results on" (filter statistics gadget). Far more useful than a predefined…
-
Oh, and the simple filter definition in 5.2 is far more friendly for defining filters.
-
No, it doesn't. Personally, although I can see the logic behind it, I find it's actually a bad idea. I save and share the more obvious "base" filters for people and then invest a little time in showing them how to take a base filter and extend or modify a copy to suit themselves. Teaching people to filter seems to be far…
-
Go back into the workflow view and look for the edit button - that will automatically create a draft and let you make amendments.
-
I'm afraid you're going to need to do some more digging then. If your permissions are correct, then you should see issues. If you can work out the key of an issue you should definitely be able to see, then can you try the direct url for it? i.e. http://yourjira/browse/ABC-123
-
This sounds like you have administrator rights, but not actually "browse project" Have a look at the permission schemes and make sure you are in the groups or roles that the permission scheme says "browse project" for. (Note that "admin can see/do everything irrespective of permissions" is a bad security model and hence,…
-
Yes, but it's hard work. The most simple migration will need to: * Manually set up a project for each of the migrating projects, including all the schemes, fields, workflows etc (Note that there are add-ons which can make this a lot easier) * Upgrade your 5.2.11 installation to the same version as the target system (you…
-
>Basically our plan is to configure new Standalone JIRA Service Desk application setup (latest version) on separate server machine and wanted to integrate it with current JIRA setup (which is on 5.2.11). Right, that is probably the worst possible thing you can do here. You are effectively saying you will have two separate…
-
1.1 is the highest. I'd very strongly recommend a JIRA upgrade to at least 6.4 to remain supported and enable higher versions of JSD (JIRA 6.3 support goes away this month, so you want to be on at least 6.4 as soon as possible)
-
You can create new issues whenever you need to - in this case, I'd strongly recommend one per subject (e.g. I ring you six times, the first three calls being about my cat, my dog and my bunny. You fix the cat and bunny first time, but the dog is a bit of a pain and I have to ring again a couple of times. I'd expect three…
-
I couldn't agree more - JIRA Service Desk on its own can do that quite well as long as your users are ok with the "documentation" being a string of issues. A better solution would definitely be to add Confluence to it so that you can generate knowledge-base pages directly from calls with a single click (and I actually…
-
No. Security by IP is a bad idea, but that's a different question. If you want to do it, you can't do it in the application, you need to do it before the application, which means via your proxy, firewall, network filter etc. If you're with OnDemand as your label says, I don't know if Atlassian will do it - raise a support…
-
Neat trick, but it only adds to the database, Jira is unaware of the data. Unless you've coded something to expose it?
-
Neither of those activities are date stamped in Jira, so you can't really do it. The closest I've got to working out a project creation date is to narrow it down to "when was issue-1 created", which might not be that helpful if you work in a place that creates projects well before they actually get used.
-
That tells us that there is probably an issue with your LDAP connection timing out, and you need to check the timeout you've set is valid for the response time of your LDAP connection.
-
As an admin, go to Admin -> User directories and check the status of the active directory connection. If that is not working, you will need to work out why and re-enable it. If it does say it is working, then you'll need to look at permissions and the groups that can log in. In both cases, reading the <JIRA…
-
Loads. Actually, the basics are built into Jira's workflow stuff already. Open up a workflow and look at the transition(s) you want to restrict. You'll find they have Conditions, Validators and Post-function tabs, and these are for: * Conditions - if the conditions are not met, the user will not be offered the transition…
-
No. You can either see an issue or you can't. (You can restrict comments to groups, as they are entered, but that's done as you enter/edit it) There are plugins that might help, but I don't think any of them are available to OnDemand.
-
The previous answer still stands, I think. In your use-case, you could probably code something to make the number "jump" quite easily, but you'd need to stop the users creating issues completely. Simple reason - Github creates branch 300, then users create 5 more issues taking the counter to 305, then Github creates branch…
-
I'm not sure what you mean by auto-generated - do you mean Jira will be generating the number itself, or that the external tool will push the number into Jira, or that Jira will pull it from the tool? All of these are going to need a spot of code, but there's no point me rambling through details on one of them if another…
-
No Sorry that's so terse, but the issue key is embedded so deeply into Jira, there's no way I'd even begin to try to do this. Might as well use the other tool instead if it's important. The basic workaround is doable though - define a custom field for the external key and store it in there. If you're willing to do a little…
-
A select list has a list of options. You set the options. Doesn't matter if it's (Name, URL), (Badger, Mushroom, Snake) or whatever. Actually, I'm really not sure I understand what you mean by a composed field. However, I suspect labels are even less suitable, as they break down into single words, so entering name, url…
-
To get a pre-populated list, ditch "labels" (the whole point of the labels field is that users can enter what they want without a fixed list). Create a multi-select list instead, that has all the functions you need.
-
Are you running it behind another web server? Apache or IIS for example? It's *very* common to run it behind Apache, and the things you are seeing are symptoms I've seen when the Apache and Tomcats are not talking to each other properly, so I thought it's worth asking to rule it out.
-
Sorry, I edited your question title because I almost typed "run filter, use bulk edit", and that's not what you meant. Sadly, I'm also afraid I don't have an answer for you - there's no way to correct the filters that have been broken by the rename.
-
The usual problem with "I can't bulk edit" is that you have not granted "use bulk edit" permissions in the Global Permissions under admin If it's not that, then you need to give us error messages or explain what "I'm unable to use" means in more detail.
-
What "token"? What does "make images open" mean?
-
Debug the filters and check the settings on the gadget. The issue navigator is pretty much the definitive place to start - you can be sure that when it tells you "this filter returns 400 issues", then there are 400 in the filter. It sounds like the gadget is pulling out more than the filter, so with that, you need to check…
-
Then your question is irrelevant, you don't need the component accessor, you have no access to it.Use the REST APIs as documented, and Gabor's point to see if Agile is installed.