Ignacio Pulgar Expert

In the page where you add fields to the screen, you can drag and drop the fields to display them in the desired order.

Glad to hear that! Would you mind accepting my answer? Thanks!

By the way, I once saw a screwed burndown chart just because a user had set 1,000,000 story points to a story as a joke. After the laughs, they corrected the story points value, but as the burndown chart had to display the estimation change, it was being displayed at a scale to show up to 1 million story points, therefore,…

In order to prevent this situation from happening again, I would suggest including the Closed status in the workflow (if it is not already there) adding to it the property jira.issue.editable with value 'false'.

If you have disabled the preference of being notified of your own changes, then you will NOT receive notifications when you update an issue, even if you are a watcher of that issue. The preference of not being notified of your own changes is just for mere convenience of a large group of users who think: "If I am the person…

The only possibility I can think of at the moment is that it might be shown a custom selection of fields, instead of all fields set to be potentially displayed. Can you try this from either the Create or Edit Screen? Note that the View screen won't generally show a field unless it has a value set, with some exceptions, so…

Have you tried the Epic Burndown chart?

"How many people would you hire for picking up the phone in that company?" That's the question I've heard in order to calculate the number of Service Desk agents. It is important to know that Developers without a SD agent license can add just internal comments, not viewable by SD Customers. Note that at least one person…

Boards do not belong to any projects, despite of the fact that they are shown from the project view if you have access to both the project and the board. So, there's no place to which the board belongs. A board which is fed by issues from multiple projects will present all statuses from all workflows set in every project,…

Let me ask some questions in order to better understand this use case: * Who exactly is supposed to set the approvers and based on what criteria? * Can the list of approvers be known in advance? * What's the selection of an approver based on?

Hi Craig, That is not possible yet, but you may want to vote for these feature requests: * Ability to add/remove columns/filters in My Request page * Ability for customer filter issue from "My Request" page using JQL query Regards.

The display of worklogged hours in a time frame is not provided by natively by JIRA. The cheapest addon I know that can help you getting that view is Time Reports (Server or Cloud). Alternatively, you can go for eazyBI addon, which is more expensive but it provides you with many other reporting capabilities.

The documentation of the expression function contains a section named conversions which states: Users A String containing the user key. This is sufficient as they are just used for equality comparisons So, I'd say Script Runner supports username equality comparisons.

Are there more boards which display those issues? If that's the case, do all of them have the 'Completed' and 'Sign Off' statuses mapped to the most-right column? This would be a typical cause of story points not being burnt.

Hi Sahar, The easiest way to separate all 4 departments in the intended way would be having 4 different Service Desk projects, each with its own Customer Portal's URL and, optionally, its own email address channel. That way you would be able to easily set each SD project: * Viewable just by the correct department, by…

I guess you have added the group directly into a permission scheme that it's being used by other projects. I would suggest adding that group to one or more project roles (ie: Users, Developers, Administrators) in the projects you would like that group to have browse projects permission.

The eazyBI Support Team solved this question (thanks Martins!): It is possible to import issue Description from JIRA into eazyBI by using JIRA MISC calculated custom fields. In order to do that, at first, you could create a new JIRA MISC calculated custom field (with text type): And use this following formula in the field…

Yeah, IN (user1, user2,...,userN) works. There are some groups with a lot of members where that approach might not be so handy, though. Glad you have worked around it in a good enough way 

That's right. What it is a little bit weird is the fact that I've been able to use it successfully; despite of the red cross being shown, the correct list of issues seems to be retrieved...

mmm... that's strange. I'm getting the following error message: "A value provided by the function 'membersOf' is invalid for the field 'assignee'." I confirm I've used a valid value (an existing group name). Googling it, I've found this response. In a nutshell, it is not working because your group Support contains at least…

You can do it by creating custom fields. In order to do so: * Enter JIRA, press the 'g' key twice and type 'custom fields'.* Click on the button 'Add Custom Field', on the top right corner. * Select a text field (multi-line or single line). Click 'Next'. * Give it a name and, optionally, a description. * Click on Create. *…

I'm not a native English speaker, but I think that "additionally to enter text" is quite ambiguous, as it may be interpreted also as "an additional option besides of entering text". Based on that quote, ambiguity might be decreased (if not suppressed) by using a more appropriate phrase like: * Alternatively to enter text…

issuetype = Bug AND summary !~ "*On Production*" Try with 'text' instead of summary, as I can't test now if it works as well.

There's no such an addon for free. The cheapest one is Time Reports (either $5 or $10 per month, depending on the number of users of your instance).

Hi Piotr, That's not doable at the moment. There was a feature request for that, but was rejected by Atlassian with 'Won't fix' resolution. Please check: https://jira.atlassian.com/browse/ID-6167 While I was one of the users who initially voted for that feature request, I understand that it would potentially cause security…

The most similar thing to what you have described is Who's looking for JIRA Cloud, but just shows the list of users who are looking at the issue at the time you are looking into the issue. Hope it helps.

@Jaime Silveira In Jira Cloud, as much as I've tested, the permission subject 'Reporter' doesn't seem to work as expected.Instead of referring to "the person who was the reporter of one or more specific issues", it seems to act as a much wider "group of people who have Create Issue permission".Therefore, I think it is not…

@Duco Zitman: I have tested it and you are absolutely right! Clicking on the Edit button you cannot edit the Original Estimate field (it's not even shown), but it is shown and editable by pressing the shortcut 'e'. Looks like a minor bug... What do you think?

Extract from official documentation: If JIRA's Time Tracking feature is in Legacy Mode and work has not yet been logged on the issue, you will see the Original Estimate field. However, once work has been logged, you will only see the Remaining Estimate field. From Legacy Mode: If Legacy Mode is enabled, your users can only…

What you say can be done, and needs no special approach: Just create the projects you expect to need and add as many issues/tasks as you need to. What can you do if the project is not still active? Grant access to this project just to the users who are going to create the provisional tasks. For all the remaining users, the…