Comments
-
My guess is that you are using Exchange, which has a proprietary protocol called MAPI, which is expensive and pointless to implement in most software. Your best option is to enable IMAP on the Exchange server for the incoming mailboxes, but if your admins refuse to upgrade the available protocols to IMAP, then the only…
-
I'm not confusing anything, but you were very unclear about the role. We've now got three - admins, authors and process owner. Authors don't need admin. Admins do. The process owner is a grey area. To do that job, technically they still do not need admin, but they should be an experience user who knows the potential power…
-
Yes, it will affect all existing risks and issues (assuming the field configuration scheme says it should apply to both types). You will find that the issues work fine for search and view, but if you try to edit or transition the old issues, Jira will demand that you fill in the fields before it lets you save any changes.…
-
You'll need to define what you mean by "escalation matrix" and decide what you want its effects to be. Then we can help you build something.
-
If you want them mandatory on create, then use the "field configuration scheme" as I said before. That is covered at https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html
-
Ok, I asked because I have a feeling the new "agilty" projects don't have categories. A Software project will have it, so either you don't have the rights to edit the category, or it's been disabled somehow.
-
Create the account(s) you want to administrate Confluence in Confluence, then add to the group(s) named as administrator groups in "Global Permissions".
-
Eh? I just said "remove them". I woudn't have said that if you can't
-
See https://confluence.atlassian.com/adminjiracloud/advanced-workflow-configuration-776636620.html
-
If you are on a Server version, then you can use any version of Jira you want, that was released before the end of your licence. But be aware that you can not downgrade your data - if you do decide to go back, you will want to re-start with an empty Jira (and probably import some of the data via CSV) If you are on Cloud…
-
If you want it to be mandatory from the point of "create issue", use the "field configuration scheme" to set the fields mandatory. If you want them to be mandatory later in the workflow, you will need to add "validators" to your workflow to force people to enter them at the right point.
-
Get your admins to add them from Admin -> Issues -> Custom fields -> (Accounts) configure
-
There is no "bulk create sub-tasks" function in plain Jira. If you had one, it was provided by an add-on which is no longer active. You'll need to ask your admins what was providing it before and to get it re-enabled.
-
That looks like a custom field, which means the list of accounts is set by your administrators. If you only have two, that's because they've only defined two (for this project)
-
Time tracking in Jira is done in days/hours/minutes, not dates. My guess is that you are looking at a date field, not the time tracking fields (and also a field defined as just a date, not a date/time). Possibly due date? You're probably doing that because your Jira is not configured to use time-tracking in your project.…
-
I'd argue exactly the opposite - people responsible for the documentation should not have to know how to administrate the tool they use for maintaining the docs. Ideally, it should be easy enough for them to use without caring about the admin at all. An analogy - I have no idea how a car works, but I don't want to be a…
-
I suspect the "closed" status was not in the right hand column, but is now (which fixes it)
-
The list of available status is global, not local to your workflow. So I suspect the global list already has a status of "pending", so you can't rename another status to that. To use "pending", edit the step of the workflow and select the pre-existing "pending" status
-
You have to publish the changed workflow for the transition changes to be picked up.
-
Yes, they do count, if you add them into the agent role. If you don't add them as agents, they won't count towards the JSD licence numbers.
-
See https://confluence.atlassian.com/jira/retrieving-the-jira-administrator-192836.html
-
Jira 3.3 is so old, you'll struggle to find anything that supports it. It's also insecure and unsupportable, so I'd strongly recommend planning to upgrade it as soon as possible. Jira 3.3 does not have JQL, that only arrived in Jira 4, and the searches in 3 won't expose the history information in any way you'll find useful.
-
They're backups, often generated by upgrades. You can remove them assuming you don't want to do any roll-backs.
-
If you mean indexing in the application, go to Project -> Settings, and hit "re-index project" If it's database indexing, you don't, you'll have to rebuild the database indices for everything, with Jira offline while you do it.
-
You don't. You should move away from the idea of "assigning" things to teams, that does not work. Define queues that tell people what is next for them to pick up.
-
We don't know what your "planitems" are, as it's not something in plain Jira, you'll need to explain them
-
You can install httpd where-ever you want, as long as it's available to your users on the urls you want to use. Jira does not have a proxy built in, as not everyone needs it
-
I am not going to waste my time rewriting the docs or doing a copy and paste from them. Please read the link given. If you struggle with it, then ask again and tell us what you are not understanding.
-
No question, and no screenshot here. I'm afraid we can't help you based on no information.
-
Put a redirect in the http site.