Comments
-
Configure your workflow to use the “All” transition which allows you to transition from any status to any status.
-
My changes means that you want to be notified (email) for changes you make. If you comment on an issue you get an email. If you transition an issue you get an email. Of course this is all governed by the notification scheme.
-
Is there a value in the field? If not that could be the reason. Does it show in the edit screen if so add a value and see if it then displays in the view screen.
-
My first guess is that there is an automation involved and the “run as” is the robot.
-
I would suggest reaching out to Atlassian Support for this. I am not seeing on my instance.
-
What you could do is, while sprint is still active, break the story into two parts and move the undone to the new story.
-
First the individual should not have all of those roles, at least concurrently. They should be part of Service Desk Team. Use the “invite” menu item in you project sidebar. Next go into the User management section of the system admin area and check the individuals access to JSD. Be sure it is checked. Try that and get back…
-
To be clear, Create/View/Edit are the “types” of screens. What else can you do to and issue? What you can do, and likely are asking for, is to create uniques screens and use them for one of the three type functions. This is what @Vishwas has conveyed.
-
Is this by chance a NG project? In Classic you should see cascading as an option.
-
You can add a Condition to the specific transitions that you wish to restrict. You can leverage on of the “User in...” conditions, e.g. role, group etc.
-
If you are an admin you can go to Jira settings > issues > custom fields and add field then choose cascading.
-
This is an oft asked question the Community. The steps are as follows: * create a screen that displays the Resolution field. Note: you may already have one so check under the Screens admin page * edit the workflow in diagram mode * double-click the transition to Done/Closed. Make sure you do this for any transition to…
-
interesting. can you show me the page before that one? Here is what i see... it may be that since you are on a new instance they may only offer NG but that would be strange and unfortunate for sure.
-
please provide a snapshot of board settings > general page
-
If you are interested in setting up a Classic JSD here is what you would do this: * click on magnifying glass * at the bottom of sidebar select Projects in Advanced search * Click Create Project * Click Classic * Change Template and select the type of project, e.g. Internal IT or External Customer documentation here the…
-
arrrrrgh.....ok. i see the issue. You are using the Next-gen template which is out in beta. I have installed that as well and created a project but have had zero time to play. Let me see..... so I assume you have users under People defined w/ Agent role? I would hope, but don't know that the Agent role would automatically…
-
no the trial gives full access. are you sure you are a Jira admin and not just a project admin? if you click here to you see this?
-
when creating Kanban boards for business projects be sure to do the following: * create the board and for "Location" use your profile (at the very bottom of the list). Be sure to use a unique board name that folks can recognize. * share the board with those that need or simply "any logged in user" * in any project, e.g.…
-
you do not have the necessary permissions. you need to chat w/ your admin to have them change this.
-
Well yes sort of. Boards are not directly associated w/ workflows except sometimes they are. How is that for being vague? :-) Let me attempt to clarify this. * Issues belong to Projects not Boards * Boards are glorified visual representations of filtered lists. A board is created based upon a filter. The filter can be…
-
go to project > project settings > notification. Ensure that the role that your agents are associated with is included in the Issue Created event
-
not yet supported. here is public roadmap
-
Yes. there is a bulk update function. Basically you create a filter by searching for issues that meet your criteria, e.g. project in (a, b, c, d) and status != done and... Then once you have the list representing what you wish to close then you can use the bulk update on that same page (upper right ellipses). A few things…
-
you cannot. that is where Classic project come in. NG projects are self-contained. They work on the premise that anyone can create their own project that will have zero impact on neighboring projects.
-
what do you mean by "have access to the ticket". As a customer they won't have access to the JSD application but would have access to their issues in the portal. Do you not want them to be able to monitor the tickets they created? You can also consider a non-portal solution using the Widget feature or simply email…
-
if the avatars are associated w/ issues you need to reassign the issues. if they avatar is at the top then the users must not be "inactive".
-
@Shaikh Arif Mohd Mondal , ok so it is odd. I went to test this out and indeed the Customers will show up in the list. However, if you try to add them it will result in an error. I don't recall seeing this before but TBH don't recall trying it either. :-) It is unfortunate that this is the case. I searched JAC to see if…
-
which fields are not being exported specifically? Server or Cloud?
-
here are some open suggestions. you might want to vote/watch: JRACLOUD-63150 CONFCLOUD-43577 JSDCLOUD-7937 interesting there appears to be "darkfeatures" but you cannot change at least in Cloud it appears but have not spent time playing.
-
Barry, i'm sorry if I was unable to help. I'm really trying to understand where i'm missing the mark TBH. I am always seeking to understand how others use Jira so I can pick up on new concepts or learn from my misunderstandings. In my usage the Epic Link is not anything random at all. It contains the Epic Name defined in…