Comments
-
It's too short, and hence, invalid - you need to fill in more to get it to reappear.
-
Ok, great, that means that JIRA will "name" it "Affected Projects" (unless you rename it!), but always refer to it internally as customfield_nnnnnYou can get that nnnnn by going to the list of custom fields and hovering over the links to edit/configure/delete and looking for id=12345 in the url it links to. There are other…
-
We don't know. What is "affected projects" in your system? I ask because it's not a standard JIRA Core field name, so the question is how you've set it up, or if you've added an add-on which adds it. In either case, you'll need to explain how you've implemented it before we can help you with the name. Also, what you mean…
-
When you try to add user 26, it will stop you if you are using internal user lists. If external, some of the functions will stop working (adding issues is the main one). You will either have to get a 50 user licence, or disable users until the count is down to 25 active users.
-
I can't read your code here, but in the original post, you were giving a function that expects a *field* a *string*, which won't work.
-
I think you've fed the getCustomFieldValue function the name of the field, rather than the field object it requires.
-
Atlassian have moved on to "Teams in Space" now as well.
-
I know. Some stuff gets closed because they finally decide it's not worth it. Other stuff remains open until they have re-designed something to enable it, or it becomes worth it. If you want a real laugh, and an example of a long-standing issue, I think JRA-9 holds the record (it was about users having different timezones…
-
The service desk licence issue is very much higher up the list than those issues - the Atlassian I was talking to last night was very clear that we should expect at the very least an announcement very soon (although I really don't know if it will be "announce now and confirm in next version" or "announce new SD release…
-
Ah, there's going to be changes for Service Desk. Atlassian know they need to do something like "agent based licencing" (i.e. 10 Helldesk minions taking calls for 10,000 users - shouldn't need a 10,000 user licence, just 10 for the minions). But I don't know what shape it will be, or when it'll arrive (all I've got is…
-
No. You've answered your own question by referring to point 6 in the FAQ. You need 2000 Agile licences.
-
I think you need to decide exactly what the rule for "close sub-task" should be, as well as the rule for "top level issue". Then you need to talk to your administrators to get a look at the workflows...
-
There's two layers to it here. First, the permissions - you might have "close" permission, but that doesn't necessarily mean you can or can't close. It's more of a flag than anything else. Secondly, there's the workflow. As you've hinted, you can put conditions on the workflow. Like "user must have the close permission"…
-
Admin permissions gives you admin rights, not "everything" (because it's a dreadful access model). As an admin, you will be able to see all the projects configuration details, from the administrators project list, and hence have access to change their users and permissions and schemes etc, so you can give yourself access.
-
I'd contact Atlassian support on https://support.atlassian.com
-
In Agile, you're not expected to estimate at a sub-task level. In plain JIRA, you can, and that's where the toggle comes from, but it's not supported in Agile.
-
You could use different scripts by having different workflows, or you could stick an "if" statement into the script to check which project you are currently in.
-
You really have NOT read or understood the original answer. Let me repeat the basics * You can't upload addons to OnDemand instances, they are locked down to prevent the addition of code that Atlassian are not prepared to support. * There is a list of things you can enable in your OnDemand account settings, * Coveo is NOT…
-
PLEASE read the original answer. https://answers.atlassian.com/questions/310350/indexing-jira
-
The answer has not changed since the last time you asked this. Please read the answer you were given last time.
-
Last I heard - Answers is based on the open source system http://www.osqa.net/ but is not packaged up as a product for distribution by Atlassian. I don't know if their customisations are available generally either. I don't think Confluence lends itself to forums/q&a, but it does complement a system nicely when you use it…
-
I suspect it is the setup of your workflow for the test cases. You'll need to look at that, and your process for "passing" the cases. You've not described your setup or process here, so we can't tell you a lot more. I don't know if your test cases are a simple issue type with a self-built process, or you're using a test…
-
Very true, you need to watch out for the defaults - it is good that Atlassian have a default group for "everyone who can log in", but it's a nightmare that they also use it for "can access project" by default. It's well worth unpicking that as soon as you start using Jira, if you ever have any intention of limiting access…
-
Oops, sorry, I should have said see https://confluence.atlassian.com/display/JIRA/Configuring+Issue-level+Security as well
-
Yes. You can set "issue level security" - it's a bit more complex and flexible than how I'm about to describe it, but you can do it. Essentially, you let people see the project and all the issues in the project. Then you set a "security level" on any issues you want to hide. As far as your unprivileged users can tell, a…
-
JIRA permissions will let you do most of that - you can separate people out into sets that can view and/or edit and/or submit and/or transition, and/or etc etc etc. What you can't do is "hide planning". If a user can see an issue, that's it, they can see everything based on that issue, inclluding any planning you might be…
-
Create a normal user. Then, depending on the admin level desired: * For a project admin, add them into the project roles or groups such that they match the permission rule for "project admin" * For JIRA admin, get an existing admin to add it to the JIRA administrator's group. * For System admin, get an existing system…
-
A good component would indicate a distinct part of what your project is for. If you were building a computer for example, you might want components like memory, cpu, motherboard, case, power supply, graphics output and so-on. A poor component name would be "display", because it's not a true component in hardware, it's a…
-
>We want to create tasks and subtask automatically from another sytem via web servis. Ok, that does not need any new table or even mapping. Keep it simple - create the issues in JIRA via REST and add a custom field (not editable by users) that stores the extra mapping data you think you need.
-
Please, don't. It's a pain in the neck to maintain, you will need to write piles of code to be able to use it, and JIRA will still ignore it on migration and upgrade. What is the actual requirement that led you to this (very bad) idea?