Comments
-
Hello, if you use IN operator, then it must be assignee in ("userkey"). You can type the display name of the user and Jira will put the userkey itself.
-
Nope, I have a more dropdown near Assign button. What is your Jira version?
-
You need to configrue screens for the sub-task issue type. Find what screen is used for issue editing and viewing. Then open the screens and add Time Tracking field. Read more here about screens https://confluence.atlassian.com/adminjiraserver071/defining-a-screen-802592587.html#Definingascreen-configure
-
I see, could you open the detail issue view and there must be "More" dropdown. Then inside the More dropdown there must be Log Work button. I am not sure in what screen you choose three dots. There are many screens like that in Jira.
-
Are there no issues with Log Work button enabled in your Jira instance? Or only certain issues do not have the button?
-
Hello, Have a look at issue security schemes. Security schemes let you configure visibility of issues in a project. You can read more here https://confluence.atlassian.com/adminjiraserver071/configuring-issue-level-security-802592414.html
-
Hello, You could 1. Implement a bean which is LifecycleAware and then implement onStart event where you would create your custom fields. You can read more here https://developer.atlassian.com/jiradev/jira-platform/building-jira-add-ons/jira-plugins2-overview/jira-plugin-lifecycle 2. You could set a bean…
-
You need to 1. Find the workflow for the issue. 2. Go to cog item-> Issues -> Workflows. 3. Switch to the edit mode of the workflow 4. In the workflow choose the status in which your issue is now 5. Click view properties 6. Check if you have the property there.
-
Hello, A field will not appear on the view screen if it has no value. That is how Jira works. You need to set a value for it in the Edit screen.
-
Are you sure you checked the workflow of the issue? The part about jira.issue.editable ?
-
Or if for some tickets SLA must begin from Open Status and for some tickets from In Progress status, then you could define 2 SLAs. Default JQL in both of them would have no goal. And then you would add additional goals to each of SLAs and define with JQL for which issues each SLA must appear. If your JQL queries do not…
-
Hello, What do you mean by issue avatar?
-
If you want to use Service Desk SLA, then you can create a new SLA. Then you would have 2 SLA's for certain tickets. I really do not understand your requirements. Sorry.
-
Have a look at time in status plugin https://marketplace.atlassian.com/plugins/com.obss.plugin.time-in-status/server/overview Or you can write a custom solution by your own plugin or using Adaptivist ScriptRunner or something similair. If you are not on Cloud, you could for example make a scripted field in Adaptivist…
-
Do you mean that you do not need SLA in terms of Jira Service Desk? SLA means the counter which is shown in every ticket In Jira Service Desk. You mean that you want somehow to define how long an issue was in certain statuses? And you do not want to use SLA functionality of Service Desk?
-
I do not quite understand about components and your requirements. In SLA there is always a default JQL. If you do not define a goal for it then there will be no SLA by default. Then you can add a new goal for your components and SLA will be shown only for your components.
-
Hello, It must work in portal?
-
If you have Jira Server, then have a look at nFeed Plugin. You can customize display views of custom fields using Velocity templates https://valiantys.atlassian.net/wiki/spaces/NFEED57X/pages/52068409/Display+view
-
Hello, You can define yourself, from which status SLA shoud begin to count. You can begin to count not from Open status, but for example, from In progress status.
-
Hello, You should add only those issue links which you need. If you do not need anything else, then do not add.
-
Hello, 1. You should check that there exists a transaction from the current issue status to the one of the mapped statuses in the board column to which you move the issue. 2. Check that you have the rigths to perform this transaction.
-
Hello, What do you mean by table view? What information should the table view present?
-
Hello, I just had a look at ScriptRunner documentation and I did not find information that it supports Scripted Fields for Jira Cloud. You can have a look here http://scriptrunner-docs.connect.adaptavist.com/jiracloud/quickstart.html#_extend_and_automate_jira_via_built_in_or_your_own_customised_groovy_scripts
-
Hello, Do you have problems with Cloud license or Server license? If Server, you can change the license through database. Here is a guide how to do it https://confluence.atlassian.com/jirakb/how-to-get-and-update-jira-license-string-from-the-database-441746313.html
-
Hello, It is possible.You can.use security schemes. For each security scheme you define users or groups or roles which will see an issue which has this security level. You can read more about security levels here https://confluence.atlassian.com/adminjiraserver071/configuring-issue-level-security-802592414.html
-
The problem is that in the Edit screen field "parentIssueId" does not exist. That is why if it does not exist then you should take the value from the issue. Replace FormField parent = getFieldById("parentIssueId") Long parentIssueId = parent.getFormValue() as Long with FormField parent = getFieldById("parentIssueId") Long…
-
Hello, It would be nice to see your script.
-
Hello, Have a look at status properties. I think there is a property which forbids to edit the issue in the closed status. Kindly read the following article about status properties http://www.j-tricks.com/tutorials/permissions-based-on-workflow-status
-
I had problems with autowired in constructors before. I use inject and had no ptoblems so far. Instead of scanned i use named. also the same reason. You removed the file but it does not mean you solved the problem. You can get same error later when you call your custom field.
