Comments
-
hello, you might find this link useful: https://answers.atlassian.com/questions/268243
-
hi, you can find the instructions here: https://confluence.atlassian.com/jira/customizing-email-content-185729653.html
-
hi, yes. you need to edit your workflow and assign a new screen with the fields that you want to the Assign to Developer transition. Selection_019.png for this you need to create a new screen here: Selection_018.png
-
yes exactly, it is shown while the transition occuring and shown to the user who is making that transition.
-
hi if you need to get some input from the user when transitioning the issue, like for example when starting development you might want to learn how many days it will take to solve, then you can add a custom field to a screen and add this screen to your transition. but you don't have to add a screen, it is not compulsory.…
-
hi, here are some answers for your questions: https://confluence.atlassian.com/jira/jira-requirements-185729596.html here are prices for JIRA software: https://www.atlassian.com/licensing/jira-software/ here are prices for confluence: https://www.atlassian.com/licensing/confluence
-
hi, i was gonna suggest drag drop the bug issue type to the beginning but you already did that. Also you chose bug as default issue type. I think JIRA shows the last used issue type as the first one in the create screen. For example when i create the previous issue as "task", it shows "task" again when i click on create.…
-
hi, this link may help you: https://confluence.atlassian.com/jirakb/error-importing-data-java-lang-nullpointerexception-during-migration-to-jira-5-2-11-346325923.html
-
just like any other tasks. you click on the subtask, you start progress, move forward step by step and when you are done, click on the done buton (it can be different according to your workflow) Selection_006.png
-
hi, you can add timetracking field to the create screen of your subtask screen scheme. that way you can enter original estimate value for the subtask too.
-
hi, in the project's administration you can see automation in the left menu. Selection_006.png you write a rule here like this below: Selection_005.png
-
hi, have you tried using automation "transition on comment"? this way when customer commented on the issue, issue is automatically transitioned to the next status.
-
hi, you can use issue type screen scheme for this. create a different screen scheme and associate it with that specific issue type. add a new create screen in this screen scheme and add your custom field to this screen and you should be all set.
-
hi you can use "user picker", "multi user picker" custom fields for this.
-
hi I have a different approach. I don't know if it meets your requirements but it is a good one and we use it with one of our clients. you can create a pool of issues that are assigned to developers. you can achieve this by creating a user with a joint mail (like a mail group), adding all your developers to this mail group…
-
if I understand it correctly, you want to change the project type of an existing project to service desk, right? if so you can do it like this: click on cog > projects Selection_004.png click on change project type and select service desk.Selection_005.png I come to this conclusion because you said " I cannot find anywhere…
-
Hi, In the migration hub page it says: "If you renew your license after JIRA Software is released, you'll automatically be given a JIRA Software license (not a JIRA license). Your JIRA Software license will work with both JIRA and JIRA Agile. (In other words, you can paste the JIRA Software license into the license box for…
-
Hello, All jira licenses have converted to jira software, that means you don't need to buy a new jira agile license. You can transfer your license. Jira 7 means jira software so third question is same as first question.
-
Hello, As far as I know, Service Desk is still a project. So you should be able to do it in the notification scheme of the project. You can add the agents role and remove the clients role from the "issue commented" section of the notification scheme. Check out here:…
-
hello, this link may be helpful https://confluence.atlassian.com/jira/setting-a-default-value-in-the-description-field-166003857.html
-
You're welcome Glad to help.
-
If your team is using a different project than other teams, then you can create another screen and screen scheme just for your project. Other than that, I don't know a way that you can limit a field just for a team.
-
you are editing the workflow, right? If you are just viewing you can't see add button.
-
Yes you need JIRA Suite Utilities plugin. It's free and easy to use. You can get it from here: https://marketplace.atlassian.com/plugins/com.googlecode.jira-suite-utilities/cloud/overview
-
You can not make a field required with post functions.: "Post functions carry out any additional processing required after a transition is executed such as updating an issue field." You need workflow validator to make a field required.
-
As I said above, you can use validators to make it required. You should follow these steps: Click on: Workflow of the project > Resolution transition > Validators > Add Validator > Fields Required > Select Time Spent. It ensures that the time spent field is filled before resolving the issue. You should, however, have the…
-
Hi, * Go to custom fields. Click on Add Custom Field. Select the type of the custom field. Add it to your resolution screen. * On the workflow of the related project, click on the resolution transition. Click on Validators. Add Validator > Fields Required. Select Time Spent field. I think you need JIRA Suite Utilities for…
-
hello you can create different permissions schemes for all your projects. you don't need to use the same scheme for all your projects. just create a different scheme for the project you want external contributers to be able to see. also you can add different people and groups to different project's roles and manage it that…
-
hi, you need to perform this in your project's project permission scheme.
-
hello you can't do that without a plugin. you need JIRA misc workflow extension. https://confluence.atlassian.com/jirakb/how-to-configure-comment-field-to-be-required-in-workflow-transition-648381476.html