Comments
-
Hello, Every object added to any system makes the system work slower. But it becomes visible when there are many new objects added. Jira performance depends on many different objects in Jira. But if you add a single status, you will not notice any degradation. Just add a status and have a look. I always try to add as few…
-
@zhaoyawei You would need to elaborate what you mean. Answering your question, Jira gets a password from user input. But I guess, it is not what you are asking.
-
@Alex Beizerov It is difficult to use ScriptRunner for it, because ScriptRunner does not have mail handlers. It would be easier to use Power Scripts. But you need to write code either in ScriptRunner or Power Scripts. The plugins, which I mentioned in my first reply, does not require you to write code.
-
Hello, According to the message you are not executing the command inside the git repository. You should be inside the repository folder, when you execute the command. Use the "cd" command to move to the repository folder.
-
Hello, I guess, you turned off the new issue Jira view option. Go to your Avatar -> Profile. Find the Labs menu in the page and turn on the new Jira issue view option.
-
Hello, I am afraid, that you can not prevent a single field from editing by using workflow properties as @Bhushan Nagaraj mentioned. By using workflow properties you can only disable editing of all fields. There is no way to restrict editing of a single field in Cloud.
-
Hello, You can not do it out of the box. You need an add-on for it like Email this issue, Jira enterprise mail handler. https://marketplace.atlassian.com/apps/4977/email-this-issue?hosting=cloud&tab=overview https://marketplace.atlassian.com/apps/4832/enterprise-email-handler-for-jira-jemh?hosting=cloud&tab=overview
-
Sharing or inviting someone to edit a page or blog post does not automatically grant any permissions - they will still need the appropriate Confluence permissions to access Confluence and view or edit the page. It means that you need to grant these users appropriate permissions.
-
Hello, It is not possible. There is an open ticket for this feature: https://jira.atlassian.com/browse/BSERV-2870
-
I do not know of such add-ons. You can have a look at the Atlassian marketplace.
-
Hello, It is not possible out of the box.
-
It should be like this: def commentField = getFieldById(getFieldChanged()) if ( !getActionName()) { // check if on edit screen commentField.setHidden(true) }
-
Hello, Burndown chart does not take into account remaining estimate. It has a different logic. It looks for all tasks, which have been completed in the sprint and subtracts the story points of these tasks. You can find more info here: https://www.atlassian.com/agile/tutorials/burndown-charts
-
Hello, Kindly make sure that you have the correct permissions. https://confluence.atlassian.com/conf65/create-a-template-939700962.html
-
I just checked. That is right. The time is logged in only if you have the branch connected to the issue.
-
Hello, This feature is still in progress for Cloud. You can have a look here: https://jira.atlassian.com/browse/JRACLOUD-8943?_ga=2.162116153.445380870.1527949763-593458345.1525875113
-
I am not sure what software you use for integrating TFS and Jira. But Jira has rich Rest APi. Maybe you could add some features to integration.
-
No, you can not do it out of the box. You can add what you want to the board name
-
Hello, What kind of json configs do you mean? You can find docs about Jira Java Api here: https://docs.atlassian.com/software/jira/docs/api/7.6.1/?_ga=2.165845307.445380870.1527949763-593458345.1525875113
-
Hello, Is it a Jira Software project? Did you create a board for the project? Backlog is a board feature, not a project feature.
-
You are very much welcome!
-
Hello, Users can not add issues to boards. Issues added to boards if they satisfy the filter, which is defined for the board. That is why you should setup the filter correctly and it will do the job. You can setup the filter in the Board -> Configure -> General tab
-
No, you do not need Crowd. Kindly make sure that Confluence can see your Jira server.
-
Hello, Are you sure that your user can log work in this issue?
-
It is impossible to run a schedule job in a Service Desk automation rule. But you can use Automation for Jira plugin. You can run a schedule job there. Your cron expression would look like this: 0 0 12 ? * MON-FRI *
-
@[deleted] you are not a System Jira administrator. There must be a System Jira administrator before Jira Administrator permission in the Global permissions. You can find the whole list of global permissions here: https://confluence.atlassian.com/adminjiraserver071/managing-global-permissions-802592439.html
-
You can do automatically if you have an add-on like ScriptRunner, Power Scripts, Automation for Jira. And even having these add-ons, it would be easier not to create a sub-task but a task and link it to the main task with a custom link. If you do not have such add-ons, then you can do it only manually.
-
It is also not possible. There is no JQL to find moved issues out of the box. You would need an add-on for it. For example, Jtricks plugin. There a JQL function called movedIssues: https://www.j-tricks.com/jqlt-issue-functions.html
-
I think you do not have rights of System Admin. Have a look in the global permission scheme. I have it in Jira 7.9
-
Hello, What kind of links do you use between story and sub-bugs? If you use subtasks for sub-bugs and bugs are usual tasks, then the link will be lost. If you want the link to be untouched, you should link Story and Sub-bugs with a custom link not with task -> sub-task link .