Comments
-
No that's true, you could take a look at the scriptrunner plugin for that. Or you could remove your custom fields from the edit screen (which causes them to be uneditable inline) and use the post functions on the create transition. Both are options. Best regards, Peter
-
Hi Yossi, You could take a look at the JIRA Suite Utilities plugin wich has a post function to copy field values. https://marketplace.atlassian.com/plugins/com.googlecode.jira-suite-utilities Best regards, Peter
-
Hi Yossi, You can use the field configuration for your project to simply hide those fields (they will not show up on any screen you will be using. You can now replace them with a custom field of the type Single Version Picker. I hope this helps. Best regards, Peter
-
Hi Paul You could just use the external link field to link your issues with the corrsponding documents or pages in your enterprise document management system. Just an idea. Best regards Peter
-
Hi Neeta, You can go to your System General Configuration in the Admin pages of JIRA. Here you can define what is being used as From address name in the Email From setting. If you use ${fullname} it should replace the jira-admin with the name of the user executing the action that causes the notification. Best regards, Peter
-
Hi Rumi, These links might help you too : https://answers.atlassian.com/questions/52179/multiple-repositories-for-single-crucible-project https://confluence.atlassian.com/display/FISHKB/How+to+add+several+repositories+to+one+project+in+Crucible Best regards, Peter
-
1 crucible project should be enough, your users can create reviews from fisheye and can indicate the project they need in Crucible, it's explained here : https://confluence.atlassian.com/display/CRUCIBLE/Creating+a+review+from+FishEye I hope this helps. Best regards Peter
-
Hi Roland, You can just create a custom field of the type version picker for this. But all values (for both the fields) need to be defined as versions in the project. What is your exact use-case? Best regards, Peter
-
Hi William, Did you check your log files? They might give you the answer you are looking for. Also, why are you installing such an old version of Confluence? Best regards, Peter
-
Then I can only wish you good luck. Best regards, Peter
-
Thank you Rick, That query would indeed return the correctly sorted results. But seems you've run into the following problem :https://jira.atlassian.com/browse/CONF-30114 If you take a look at the comments you might find a solution. Best regards, Peter
-
Hi Rick, Does the query you use in the Jira Issues Macro contain an Order by statement? Could you copy and paste it here please? Best regards, Peter
-
Bob, Have the issues that still show up changes that have been done since monday? Best regards Peter
-
Could it be that it should be like this : SearchIntent = parentsInQuery("status in ('this week', today)" AND NOT (status changed to Done after startOfweek())) ORDER BY status DESC, Rank ASC
-
and not (status changed TO Closed after startOfWeek()) there ya go :)
-
Bob, Add the following JQL to your filters, that should help : and not (status changed TO Closed AFTER -5d) Best regards Peter
-
just use sprint = "Your sprint" instead of inSprint("Your sprint") that should work. Best regards, Peter
-
Hi Riptupurna, This seems to be this issue : https://jamieechlin.atlassian.net/browse/GRV-316 and https://jira.atlassian.com/browse/GHS-9726 Updating your version of scriptrunner should fix this. Best regards, Peter
-
Hi Julien, People can add extra people on their tickets, as explained here: https://jira.atlassian.com/browse/JSD-269 But it's not possible to do this by default, that feature request is being tracked here: https://jira.atlassian.com/browse/JSD-270 Best regards, Peter
-
Hi Julien, You can easily create a service desk portal per client and restricting access to it so only people from that client can see that service desk portal. Also keep in mind that only the person creating an issue can actually see this issue in the service desk portal, so if user A creates an issue user B will not be…
-
Karthik, This template only defines the email template you'll be using. So for your custom event I would use the Generic Event template in OnDemand. Then you can define in your notification scheme who needs to be notified when this event is thrown. And you can use it in your workflow post function. As Nic already said : in…
-
Hi Flavius, As far as I can see the are linked with the OR operator, so if either of the conditions for Start is valid the timer will start. Best regards, Peter
-
Hi Rumceisz, You should first migrate to the latest JIRA 5.x version (which would be 5.2.11) Then you can upgrade to the latest JIRA. Best regards, Peter
-
Hi Richard, We use the JEMH plugin for our emailing needs and it can automatically create inactive users (based on the emailadresses) and add these users to a user group. JEMH: https://marketplace.atlassian.com/plugins/com.javahollic.jira.jemh-ui You could then grant browse access to only this user group and your project…
-
Hi Alexander, You can use the following jql to do just that : 'assignee was <username>' save this filter and you can then use it on your jira dashboard gadgets to generate the report and data you need. Best regards, Peter
-
Could it be that the filter you are using for your task board only contains issues in the old steps?
-
Hi Eric, If you are using a proxy you could see if you could simply redirect all requests for the JIRA Dashboard to the Service Desk. I don't think it's possible in JIRA. Best regards, Peter
-
Hi Joe, You should go back to the workflow where you added the screen to your transition and go to the post functions (if you are using the new workflow editor there will be a link on the right of the screen after you've selected the transition, otherwise you'll need to select the transition and click on the cog next to…
-
Hi Jesper, Couldn't you just use a title for the user stories summary and put the full userstory text in the description field? You can see the description filed in the issue detail view on the right side of your planning board. Best regards, Peter
-
As always Andy's wiki provides the answer : https://thepluginpeople.atlassian.net/wiki/display/JEMH/JEMH+Directives#JEMHDirectives-Priority You cannot do it with the basic Atlassian Email Handlers, but you can do it with the JEMH plugin and using the directives in the subject line. Best regards, Peter