Comments
-
The reason "none of your gadgets have the option to use summary" is because it's useless to them. It's also not a correct statement, because gadgets that list issues do show the summary. You'll need to find or write something for your case. Your misuse of the summary field is generally not useful and hence you're unlikely…
-
The sub-task's work was completed in the sprint in which its parent was completed. That is how sprints work - you don't say you've finished a piece of work until you have. Any partial work done in previous sprints is unimportant because scrum measures achievement, not progress towards it.
-
Time tracking gives you time based estimate fields. Where are you "missing" these? Have you added "time tracking" to the create and edit screens for the project and issue types?
-
There is no "actual vs estimate". The burndown works off stories being "done". You put an estimate on the story. When you move the story to the far right column on the board, it is done, and the points currently on the issue (which you might have changed) are then used. Whatever the value is at that point is the "actual".
-
Generally, making database changes is absolutely the wrong thing to do. You should never touch a Jira database unless you are fixing something, and you are 100% sure you understand what you are doing. The fact you are asking this question tells me that you do not understand. Anyway, to answer the actual question: Jira…
-
Not really. You should concentrate on fixing the problem that is stopping you from using Jira though, instead of randomly importing things you will not then be able to use.
-
Indeed. Run a filter for the issues you want to see the custom field values for, choose the right columns, export to CSV, and open the result in Excel. It's built in, you don't need add-ons or anything
-
Heh, I remember Jira 1.
-
At a guess, I'd say your board configuration is wrong. Take a look at the column configuration. I think you will find that the status "Done" and "UAT" are not in the far right hand column. Everything not in the far right hand column will be either in the backlog or in a sprint, because it's not finished yet and needs more…
-
It will, as long as Exchange is set up to allow IMAP (or POP3).
-
Ok, be completely bloody-minded about it. Can you get a user who can not add versions to go to the project administration screens, select versions and see what error they get when they add a new version, or tell us if they can't because the option is not offered.
-
There is nothing in your question that might have told us that. Do you have an appropriate scripting add-on?
-
As an admin (Jira or System), Admin -> Issues -> Screens, and click "delete" next to each one that has no issue type screen schemes or workflows by it.
-
It is admin. On server, you go to Admin -> General Configuration -> Advanced, exactly as the docs say. On Cloud, I don't think you have that option.
-
Sorry, I was unclear. By "global admin", I mean system admin. There is at least one group named in the system admin permission in global permissions, and you've been removed from it (or, there may have been many and your group was removed from the permission). You need to ask someone who still has system admin to grant you…
-
You've been removed from the group(s) that grants global admin, or the group has been removed from the global permissions. You'll need to get an existing global admin to add you back into a group that has global admin.
-
No, that would defeat the purpose of a board. Nothing to stop you creating a board just for the release manager and dropping those three columns off the main board.
-
Ah, that's because Cloud is for small Jira installations. Their own Jira is *not* a small installation, they're on Server. Which won't be getting the new UI for the foreseeable future (hopefully, at least long enough for it to be fixed or abandoned)
-
Start with https://confluence.atlassian.com/adminjiracloud/defining-a-screen-776636475.html
-
No, the fields themselves ARE "variables" - containers for data that users enter. What you're asking about is logic to automate filling the fields. All three of your rules require scripting or automation add-ons such as ScriptRunner or Automation.
-
No, I mean the logging at the server level - access.log in the Tomcat directories, although enabling http logging in here will give you stuff in the Application access logs. There is no filtering in the type of calls - it's up to you to work out which ones are which by looking at each url hit and where the access was from.
-
Your customers have very limited access to the issue interface (plain Jira with Dashboards, projects and issues) - pretty much "anonymous" access which is open to all. Try sending them to the request interface - the Service Desk Portals
-
Raise it via https://support.atlassian.com/contact - that will guide you to the right place. However, you can be sure it's already been raised, and implemented, or shut down because Atlassian are not willing to support it (I can't rememeber which and don't have the time to go check)
-
My answer would be a lot shorter: Your users are not using standards. They are all asking for different setups and configurations away from the standards. If they had a proper set of standards, then project creation would be: * Admin creates project, using shared standard schemes or the default templates - Name, Key and…
-
No. A customer can login, enter requests, list requests, email, use the portal to update requests, including closing them if they're no longer valid (and the workflow allows it for them) They can not get to the issue behind the request. A request is not an issue, it's an interface on to an issue.
-
I understand that too, it's something I think of as "infrastructure reasons".
-
@Aron Sereny- your screenshot is from Cloud, this update was for Server. Also, I don't think those advanced settings are available on Cloud.
-
Ok, so can you transition the issue from the plain issue view? Does the transition appear in the workflow bar?
-
The create, edit, view and transition screens are separate entities (although they can be shared). It sounds like you have everything right for "edit" ("level" field on screen, set scurity permission), but it's not on the Create screen. Go to the project settings and drill down through the "issue type screen scheme" until…
-
That's what I thought. Customers are not Jira users. They can create requests, respond, update etc, but they only get request access. The underlying Jira issues are only for Jira users, not customers. You'll need to add the customer as a Jira user to start with (consuming a licence)