Comments
-
Hi Aris, Did you get any errors when sending the email? And why don't you simply add the timetracking.vm to your email template?you can find in the field directory under the html/includes directory tree in your email templates folder.Best regards,Peter
-
I don't think Jira actualy keeps a record of this. You could use a hidden field and fill this in automatically during your workflow transition. This field could contain the username of the creator. Then you could filter on this field. Just an idea.
-
Hi Jan, This should answer your question : https://confluence.atlassian.com/display/JIRA/Emailing+an+Issue Best regards, Peter
-
Hi Michel, It shouldn't be a problem. Those are automatic backups and exports. best regards, Peter
-
Jan, This will not work, because the HTML macro is severly limited in Confluence OnDemand (for security reasons). Best regards, Peter
-
Hi Terry, This should answer your question about requirements : https://confluence.atlassian.com/display/JIRA/JIRA+Requirement Best regards, Peter
-
Jenjira, this problem is caused by the fact that if you exclude these issue certain of your last sprints don't have any issues at all in them. See here for similar problems : https://jira.atlassian.com/browse/GHS-7250. You might be able to change your filter back so that there is a least one issue in each sprint. As the…
-
You can always try to exclude stories with those resolutions from the board filters. I don't know ifthat will help. Best regards, Peter
-
Hi Anelisa, The only way to know in a Cloud instance is to ask the people from Atlassian Support: https://support.atlassian.com Or you could download a full backup of your Confluence instance and unzip it locally to check this. Best regards, Peter
-
Hi Rahul, As explained here: https://confluence.atlassian.com/display/SERVICEDESK/How+JIRA+and+JIRA+Service+Desk+Work+Together The current mapping between JIRA Service Desk and JIRA projects is 1 on 1. So you'll need to create multiple projects in JIRA. Do keep in mind that anybody who is using the customer portal will…
-
Hi Stefan, Can the information on this page answer your question? https://confluence.atlassian.com/display/DISC/Confluence+Section+508+Accessibility+Compliance Best regards, Peter
-
Hi Liwei, If the fields are only viewable on the view screen (the screen associated with the view issue action in your Screen Scheme) and not on any other screen (except the screen associated with the Create issue action in your screen scheme) they can not be edited. Best regards, Peter
-
Hi Liwei, If you only add those field on the issue create screen and don't add those fields to the edit screen in or any screens you use during your workflow they should not be editable after doing an issue creation. Best regards, Peter
-
Hi Silviu, No there is not, you could use confluence for your definition of done and your sprint goals. Or just hang a big banner in the office :) Best regards, Peter
-
The two options are just 2 transitions from your "In Test" status to other statusses in your workflow. Your "restest pass" will go to the "closed" status and your "retest fail" might go to a "Failed test" status. You can edit the transitions to automatically close and resolve the issue when pressing the "retest pass"…
-
Hi Claudia, You currently can not change the customer portal so it will show other issues than those created through the portal. Some more information : https://jira.atlassian.com/browse/JSD-55 https://jira.atlassian.com/browse/JSD-129 Best regards, Peter
-
Take a look at the Issue Collectors, those are a very easy way to add issues from other applications. https://confluence.atlassian.com/display/JIRA/Using+the+Issue+Collector Best regards, Peter
-
Hi Milap, Normally Jira will automatically create all users it doesn't now (it will create them in the Interal Jira User Directory). You could also migrate your users from Telelogic to your LDAP and then synchronize your User Directory in Jira, that might help. Another way is to replace all references to your old Telelogic…
-
Yes all groups will show up in each application. But only the people who can actually log into your application count towards your license limit. Best regards, Peter
-
You could create a custom field of the type Single Version Picker. That will have the same functionality and will have the name Sprint Version Number. More information can be found here : https://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Field Best Regards Peter
-
Hi Gilad, It seems we have the same problem in our On Demand instance. Did you already notify atlassian support, Best regards, Peter
-
Hi Ricardo, Can you please take a look in your atlassian-jira.log file to see if there is more information to be found there. You can find the log file in the log directory of you jira home directory. Best regards, Peter
-
Kamal, Is it only for Jira Client that you get this message? Because Jira Client is actually a desktop application, I would assume that this message simply indicates that you can now download it to your desktop. And I don't think you can dismiss it for everybody I'm sorry. Best regards, Peter
-
That kind of messages is only shown to the Jira administrator users. So it should never appear for all the other users. Best regards, Peter
-
Hi, Just take a look at this KB article: https://confluence.atlassian.com/display/JIRA/Configuring+Issue-level+Security Best Regards, Peter
-
Hi Aaron, Take a look at this answer : it might help you. https://answers.atlassian.com/questions/81746/why-does-bamboo-throw-an-exception-when-attempting-to-configure-use-of-jira-user-repository Best regards, Peter
-
Hi Aaron, You should be able to simply use your own username and password (if you are an admin user). Other wise you'll need to create a user in Jira specifically for Bamboo to use when connecting to Jira and vice-versa. Best regards, Peter
-
Did you try to just drap it out of your sprint onto the product backlog, That works for me. Best regards, Peter
-
I didn't think about how having multiple planned sprints would impact that problem, good solution.
-
Hi Werner, I just tried it (drap it from the active sprint in the plan view to the product backlog) and that seems to work, but only for issues that are still in the first column of my scrum board. Did you already work on the issue that you want to remove from the sprint? Can't you just simply close the sprint with the…