Comments
-
I have not experienced the Status field disappearing. I thought you meant “View workflow”. I would suggest reaching out to Atlassian Support.
-
Pulling the conversation back into this thread... well I see that you are on server so... unfortunately “create linked issue” isn’t a thing in server, only in cloud. 😢 you can still create a clone and move it to the JSW project but not ideal.
-
You can open a Support ticket and convey your thoughts. There even may be a suggestion open on this at Jira.atlassian.com
-
You create labels simply by adding the, to the labels field in an issue. As you type it will be obvious if it already exists.
-
It seems like you are looking for a BI solution. I wonder if EasyBI would meet the requirements. Or maybe MS BI. You could certainly export to excel and us excel for this but not ideal if you wish to use this feature frequently
-
Interesting. TBH I haven’t paid much attention to the avatars. Question - are there issues on the board being displayed assigned to the user?
-
you create a sub-task by clicking on the ellipses when viewing the task where sub-task is to be added, i.e. your second image.
-
"Epic Link" = ABC-123 this will give you all stories/tasks associated w/ the specific epic
-
the SLA time goal is controlled under the goals. you can set up different rules (time allowance) using different goals based upon some field (priority, label, etc.) You do not have to and should not use Stop to work around these exceptions. Moreover the whole idea of Pause is to accommodate for such exceptions. For…
-
my question would be - Why? What do they think stop means? In what you have shared here it seems to me you have a status "Scheduled Activity" in a 'done' category when in fact it is anything but done. It is a status where someone must make an approval decision. To me that is an in progress status but arguably it can pause…
-
that is what i was thinking you were running into. You cannot change the issuetype for a request type. you must create a new request type using the desired issuetype. Without getting into a lot of detail here, the basic reason is that the associated workflows and other configurations may be different and JSD can't…
-
clarification, burndown is associated w/ the status(es) in the righthand-most column of the scrum board.
-
Disclaimer: the following contains my opinions here so please take it FWIW. ........ wow! that is a complex WF to be sure. I would certainly try to simplify if at all possible. Where possible use the All transition and only use direct transitions where you must have order restrictions. The use of the same name more than…
-
expect so but it depends on your exact expectations and the type of project and if on server or cloud. Can you provide a screenshot of what you see and where you want to see this info?
-
From what i am reading here your workflow seems confusing. Regardless, if you want an SLA to begin where it left off you need to use Pause and not Stop. So maybe Scheduled Activity is a Pause. If rejected it should go to Closed and if approved it would start again. It would take more discussion on your WF and process…
-
Change your ‘Start when’ parameters. Please share what you have currently if you need further assistance.
-
Sie müssen über Berechtigungen zum Zuweisen von Problemen verfügen, und der Bearbeiter muss ein Agent im Projekt sein, um die Zuweisung entgegennehmen zu können. Sprechen Sie mit Ihrem Administrator. Sie können das Feld Komponenten verwenden, um Experten basierend auf Bereichen zu definieren, und Sie können den…
-
This is certainly strange. Have you tried creating another project? One other test is to try and enter the following url replacing the “mycompany” and “TEST” to map to your instance/project https://mycompany.atlassian.net/projects/TEST/issues
-
My recommendation would be to contact a nearby Atlassian Partner. They can better understand your requirements and offer options including developing something if nothing exists. best of luck and if you find a solution please update this thread.
-
To be clear here, I am not an Atlassian Partner and am not for hire under those terms. I just help folks in need to the best of my ability. :-)
-
Candy, understand that a board is based upon a query of the DB. It provides a visual view of issues that fall within that filter. So copying a board would always result in displaying the same issues. Now, that said what can then be done is to change your underlying filter to expose the issues that you do wish to display.…
-
Questions: * does this happen with all projects? * does this happen to all users including admins here is what i suggest... * retry later (i know annoying but maybe there is some temporary issue w/ accessing your instance) * try a different browser * contact Atlassian Support (given you are on cloud Atlassian is the system…
-
@Administrator , I would like to close with you on this. Do you have further questions or does my explanation make sense.
-
Richard, welcome to the Community. The other thread is referencing the addon Automation for Jira not the native Automation.
-
have you tried parentEpic in ("epic-key") e.g. parentEpic in ABC-123 where ABC-123 is the issuekey for the epic
-
what method did you use to create these users?
-
so this confirms my response then. thanks for updating the thread.
-
ok so I don't think you are using the export from the advanced search for issues. please do the following: * click on magnifying on blue sidebar * click on advanced search issues * ensure you are in advanced (JQL) mode * enter the filter I provided * click on the export (box w/ arrow pointing down) at the top once results…
-
You must use the edit issue view to edit an empty field. FWIW, I recommend setting sprint only from backlog - drag and drop.
-
That really makes no sense. What you should get is a row for every issue including either the fields displayed based on query or all fields depending on the e port option you chose. Are you on cloud or server? Can you provide a screenshot of you query results and the excel view?